.gtranslate_wrapper a.glink {color: #fff !important; /* White switcher text */}

But when the popup opens, again white text color appears with the default white background, which I am aware of. Now I would like to change the text color when the popup opens.

Other questions, 1. How to change the fonts 2. Why nice drop-down expanding the whole section/container 3. Why is the customization of the plugin very limited (at least the nice drop-down has some option to change the colors)?

Once again, thank you for your nice plugin, and I look forward to your reply.

I recently updated to version 5.0.6 of the WordPress Simple PayPal Shopping Cart plugin and am pleased with the improvements.

I have a feature request that I believe would enhance the plugin’s flexibility: Could you consider adding a custom hook in the calculate_cart_totals_and_postage() function? This would allow users to implement their own postal cost calculation routines.

Adding this hook would significantly increase the customization options available, making the plugin more versatile for various use cases. The hook could look like that:

/**
 * Custom hook to allow modification of the postage cost.
 *
 * This filter allows developers to provide their own custom postage cost calculation routine.
 * It gives access to the WSPSC_Cart class instance which can be used for additional context
 * or logic when calculating the postage cost.
 *
 * @since 5.0.7
 *
 * @param float        $postage_cost The default postage cost calculated by the plugin.
 * @param WSPSC_Cart   $this The instance of the WSPSC_Cart class, providing
 *                           context and additional methods/properties if needed.
 * @return float The modified postage cost.
 */
$postage_cost = apply_filters('wspsc_custom_postage_cost', $postage_cost, $this);

Many thanks for the good work,
regards Valentin

And it’s also showing on the frontend:

But the issue is when I submit the form it’s indicate the error called “File is a required field and can not be empty.” I already try to attached different file type but the error remains the same so can someone help me with that it’s gonna be a very much appreciating.

I have two problems with Bricks and meta description generation and I think Slim has something to do with them.

1. It seems that Slim doesn’t use post extract, if it is filled, to generate meta description for posts, but renders the content of the post and keep the first few words.

But in Slim’s post metabox, if no meta description is filled, post extract is displayed as placeholder, if filled, so users believe extract is used, this is very confusing and misleading.

I think Slim should ALWAYS use post extract if it is filled and if description in metabox is empty. ONLY if BOTH are empty, then render content.

I added this PHP snippet to fix this:

add_filter( 'slim_seo_meta_description', function( $desc ) {
    if ( is_singular( 'post') )
        $desc = get_the_excerpt();
    return $desc;
} );

2. When Slim generates meta description from content, H1 title is included at the beginning.

But most of the time, if not all the time, my H1 titles are equal to meta titles, so meta description always replicates the meta title, which is useless and harmful since there’s few characters left for the actual description.

Sometimes there are also category tags or post meta like date or comments at the beginning of post content, and they are included in description, which is not wanted.

As a conclusion of this and also for performance purposes, I really think Slim should not mess with meta descriptions and leave user decide if he wants to leave them empty or not.
Google renders them better than Slim, anyway, and it will push user to write a correct description.

Thx and have a good day!
Yan

Best regards
Fariha Rehman

Regular Price 50$ – Sale Price 40$

How can I do this?