tezalsec

Hi, thank you for your efforts.

You are right, I just tested it, it is being caused by the caching. I am using the Supercache plugin, and when I exclude pages with cookie ‘s_gdpr_c_c_cookie’ in the settings, the issue stops.

However, I assume you don’t expect me to leave this setting like this? That would mean I would have to stop caching all frontend pages just to get my cookie plugin to work correctly. That would be the same effect as just disabling my caching plugin, as the cookie exists on all pages.

Should all cookie plugins not account for caching mechanisms? Have other cookie plugins not solved this issue? I would think so, otherwise caching & cookie plugins could never co-exist.

Thank you.

Regards,
Tez

Hi @niklasinpsyde, yes, the log entries seem to have ended.

Thanks.

I am confused.. older versions also behave that way, showing a cookie per page, and accepting the banner does not stop the banner on other pages on the same domain. So to completely suppress all banners you have to visit all pages and accept on all pages.

is this intended behaviour?

• This reply was modified 2 years, 6 months ago by tezalsec.

Hi, I am sorry to say, the update seems quite buggy. Now the banner only disappears after accepting PER PAGE, which is annoying to visitors. So after accepting on page 2, and then visiting page 3, the banner still appears on page 3.

Maybe some architecture error when implementing multisite?

It also does not appear on homepage, only other pages..

I am reverting to previous version, and mark this plugin ‘never update’ for now.

Thanks.

• This reply was modified 2 years, 6 months ago by tezalsec.

Hi, thank you for your response.

I tried it on some other sites, and had the same issue. Unselecting it while updating other plugins works fine.

What did worked, was to download the latest zip file and upload to update.. this did not cause a freeze. I’ll have to repeat that on all my sites.

Another thing I noticed, is that the banner did not immediately appear after the update.. I had to save your settings page to have the banner appear.

One last thing, could you maybe place the plugin link under settings, instead of in the parent left menu? Cookies is after all a modest subject. ??

Thanks and cheers!

@bojankatusic , sorry, I won’t, too much hassle.

Companies make getting feedback way too complicated these days. Logging via external services, too many steps to follow. How much quicker would it be to just embrace any good idea posted and dump it in there yourself? Especially when an idea is solid, small, and implemented fast and easily .

Up to you to disregard or add it. Thanks for considering.

@daanvandenbergh ,

I checked, the function is missing in the file class-caos.php, and at line 138 of that file is the start of the function set_file_aliases().

Yes, probably a discrepancy in commit files and local files. Good luck restoring.

Same issue on several sites here.

A simple windows search on ‘get_current_file_key’ in the folder wp-content\plugins\host-analyticsjs-local\includes gives no results..? It looks like the function is non-existent, or a file containing the function is missing or corrupted.

The issue is fixed in 3.9.1

@tamirat22, hope you are reading this and picking it up.

These are not small upgrade issues, I suspect the businesses of many thousands of people, using woocommerce + astra + child theme + overriding email template files, are now sending out corrupted emails, and most of them probably don’t even realize it yet!

Hope for a fix soon! Thanks!

Same here! So glad to be reading this, I thought I had wrecked stuff. Spent hours debugging, not finding the cause.

Weird thing was also that resending the email from the WC backend DID work as usual, correctly overriding it, just not the initial email. Go figure!

Thanks @bodybuildinggeneration , for pointing out astra as the cause! Curious how you found that out!

Astra Team, please fix asap, customers getting faulty emails ! Thank you.

Same here! So glad to be reading this, I thought I had wrecked stuff. Spent hours debugging, not finding the cause.

Weird thing was also that resending the email from the WC backend DID work as usual, correctly overriding it, just not the initial email. Go figure!

Thanks @bodybuildinggeneration , for pointing out astra as the cause!

Cheers.

Hi @paulam11 , any progress on this?

It can’t be a large issue, supporting the iframe specifics that bitchute and rumble use. It is an obvious improvement. I have not seen any new functionality added the last 5 months, only fixes. I hope the plugin isn’t standing still in adding functionality.

Thank you.

Cheers.

• This reply was modified 2 years, 7 months ago by tezalsec.

thanks, weird indeed. I decided to hack and simplify the autoload file, and removed the file_exists check, now it is all fine.

The function is a typical PSR-4 autoloader implementation for the MaxMind\DB namespace.

function mmdb_autoload($class): void
{
    /*
    * A project-specific mapping between the namespaces and where
    * they're located. By convention, we include the trailing
    * slashes. The one-element array here simply makes things easy
    * to extend in the future if (for example) the test classes
    * begin to use one another.
    */
    $namespace_map = ['MaxMind\\Db\\' => __DIR__ . '/src/MaxMind/Db/'];

    foreach ($namespace_map as $prefix => $dir) {
        // First swap out the namespace prefix with a directory...
        $path = str_replace($prefix, $dir, $class);

        // replace the namespace separator with a directory separator...
        $path = str_replace('\\', '/', $path);

        // and finally, add the PHP file extension to the result.
        $path = $path . '.php';

        // $path should now contain the path to a PHP file defining $class
        if (file_exists($path)) {
            include $path;
        }
    }
}

spl_autoload_register('mmdb_autoload');

Line 41 is the one containing the file_exists function:

‘if (file_exists($path)) {‘

I should add I am using an early loading mu-plugin phpfile containing the statement:
‘use MaxMind\Db\Reader’, making the class available to me there. The global scope from this class seems to interact with your plugin somehow..

Thank you.