Forum Replies Created

Viewing 15 replies - 46 through 60 (of 90 total)
  • I’d like to point out that the topic starter does not appear to ask what version of PHP is the minimum requirement for wordpress, but what wordpress version is the minimum requirement for PHP 5.3 and 5.4.

    If not, then I would like to ask that question

    Example: minimum requirement for Drupal 5 is PHP 5.0 (or even 4). it will MOST DEFINATELY NOT run on php 5.4.

    so how would we express ourselves to ask for the needed information that is at least as important as the minimum requirements…

    How about this;

    What are the max compatible versions of PHP for WordPress?

    I would like to see a list that states something like this;

    WordPress 3 ~ 3.5 will not run on PHP 5.4
    3.6 ~ 3.9 will not run on PHP 5.5

    And with that, looking back at the question by the TS, is the question asked by the TS

    thank you all ??

    Hi Artystyc, please don’t get me wrong; no offence was taken, don’t worry ??

    I am – however – very interested on what the problem was. But reading “it works” is good enough for me ??

    There are two possibilities;

    1. The cookie plugin fails,
    2. Your implementation is wrong,

    please try to deactivate (or even delete) the cookie plugin and check you analytics. To be sure; wait 2 days and check google, but the “real-time” option of GA should suffice.

    if you still do not get any hits (and you’re sure that’s not because of filters, or a misconfiguration of the GA plugin, then it’s probably the way you use the Cookie plugin.

    It’s vague, I know, but without any code or even a web address, there is no way for me to determine what the problem is.

    When all is installed and it “should work”, open your site, be not logged in, accept cookies, refresh the page, check the source. If you see the GA javascript code, then the problem is most likely not in this plugin.

    Again, without more information, I cannot be sure.

    “I can’t find out if any code has been added to other files outside of the plugin’s folder”
    Sorry, what?? There is only one way code can be added to other files, especially outside the plugins folder, and that is when you did it yourself. Since you ask, there’s probably not. This plugin does not change any files on it’s own.

    hmmmm, looks like the latest version does not yet have a callback on “save”, though I would have sworn it did.

    Anyways, since the cookie-prefs are saved on change of the checks themselves, you can just bind a click event;

    jQuery(document).ready( function() {
    jQuery(‘#cookie_opt_in_container button.coia-ok’).live(‘click’, function() { setTimeout(‘document.location=document.location.href’, 100); });
    } );

    Add this script to the footer of your site, any valid WordPress way you like.
    (You can place it in footer.php, with a < script > tag of course, or you can create an action hook with add_action(‘wp_footer’, …).

    we noticed that too; delete + new is a working work-around, we fixed it more dummy-proof by adding this line;
    delete_user_meta($user_id, PKG_AUTOLOGIN_USER_META_KEY);
    around line 269

    if ($cleanedKey) {
              if (!add_user_meta($user_id, PKG_AUTOLOGIN_USER_META_KEY, $cleanedKey, True)) {
                delete_user_meta($user_id, PKG_AUTOLOGIN_USER_META_KEY);
                if (!update_user_meta($user_id, PKG_AUTOLOGIN_USER_META_KEY, $cleanedKey)) {
                  wp_die(__('Failed to update autologin link.', PKG_AUTOLOGIN_LANGUAGE_DOMAIN));
                }
              }
            } else {

    @developer:
    the problem is that update_user_meta reports FALSE when updating fails and WordPress considers trying to set the SAME value as a FAILED update.

    3 possible solutions;
    1. do not call update_user_meta if data hasn’t changed
    2. pro-actively remove any existing code (like we did)
    3. ask WordPress to not return FALSE in case of “Tried to update with same value” which in fact should not be FAILURE.

    Good luck!

    Yes it is!, since version 1.2.0

    After installing and activating WPML the settings panel will allow you to enter text for the selected content-language. (WPML offers a selectbox on top of the admin screen for that)

    indeed, the cookie plugin does not do anything with the permalink structure.
    you could try if it helps to just re-save the permalink settings.
    Go to wp-admin, then settings, permalinks and just hit save.

    yeah, there is. use the .PSD files to create your own translated images and add them to the stylesheet as done with the currently available buttons

    no response in 2 months, I assume the problem is resolved.

    Latest version is 1.5.5 but the site only shows me 1.4.4, I do not know why, but you still need 1.5.5

    Edit: Ah, now it does…. wonder why it took 2 days…

    thank you for the details.
    These errors are already fixed in the latest version.

    I’ll be posting a new version soon, please try again after.

    Set “Deny all functionality until user has voted (opt-in)” and with each cookie type set ‘Default value for new visitors” to On.
    That should do the trick.

    About the refresh, I’m not going to implement that, sorry (don’t have the time), but you can do it yourself.
    There’s a bit of javascript that is executed upon clicking the ‘save’ button.
    Add the line document.location=document.location.href; and your page will reload.

    Tested with WordPress 3.6 with and without WPML (site press-multilingual-cms) 2.9.
    Works perfectly.

    Having problems? please post them in detail.

    It would be better if it stops the cookies until the visitor accept the message. Actually, some cookies are installed automatically before the plugin’s message was accepted.

    That’s a setting. Please refer to the settings panel.

    Don’t show the admin panel right [in wp 3.6]

    Have not had the chance to look at it, will report soon.

Viewing 15 replies - 46 through 60 (of 90 total)