Forum Replies Created

Viewing 15 replies - 91 through 105 (of 154 total)
  • Thread Starter dccharron

    (@dccharron)

    You are correct that this has happened before. I used the WordPress Updates page to do the upgrade. I wondered if the problem with not re-activation is due to the way I have used one of your geoip functions in my child theme’s function.php If the process of re-activation calls my functions.php which then fails due to the lack of geoip function. I then have to take remedial action by commenting out the call to your function, manually re-activating, then uncommenting the call.

    I’m going to add that test you recommended (function_exist) to my functions.php and let you know how it works in your next update.

    Many thanks @aand

    You’ve hit the nail on the head. Unseen garbage characters must have also been the problem I had.

    I couldn’t get ANY redirections to work and was about to give up when I read your post.

    I tried retyping (rather than using copy/paste) the URL. Bingo! Worked right away. What a strange condition to encounter in a plugin which has obviously been around quite a while and seems to have a lot of devoted followers.

    Again, many thanks for this useful tip.

    Thread Starter dccharron

    (@dccharron)

    This problem was not related to your plugin. It was related to WordPress itself. I deactivated your plugin and deleted it and then tried to upload the images using the native WordPress media tools. I got a similar error message (just the last part changed to
    class-wp-image-editor.php on line 419
    I repeatedly tried to get a number of images uploaded using WP Media Add New and they repeatedly failed with “Maximum execution time of 30 seconds exceeded” error.

    I edited my wp-config.php file and added the line:

    set_time_limit(60);

    I added this just below the line:

    define('DB_COLLATE', '');

    Presto, it fixed the problem and I was able to upload a large number of images of varying sizes without error. I suspect (though haven’t tested it yet) that your plugin was not at fault and I will re-install and use it in future. Thank you.

    I will change the status on this post to “resolved”.

    Thread Starter dccharron

    (@dccharron)

    I thought all plugin’s were deactivated during their update process and reactivated after the update? So isn’t the problem that the “reactivation” didn’t work? If it had, then the functions.php would not have detected a missing api function.

    Yes I updated using the WP backend (admin page). I do each plugin separately so that I can tell which one has caused a problem. It makes it easier to fix.

    In a way, I’m glad I haven’t put the function_exist test because that way I got alerted that there was a problem. If I had the function_exist test I might not have noticed that Geo IP detection was not working properly. This way I took action to fix the problem.

    I had not realised you could test is_admin. I’ll consider that.

    Thread Starter dccharron

    (@dccharron)

    I managed to get the plugin to work again. Here’s what I did:

    0- I had commented out the faulty line of code in my (child) functions.php to get back into my WP admin page.

    1- I found that the GeoIP plugin was updated but was not Activated. So I Activated it.

    2- I went into the “Options” page for this plugin and clicked on “Update Now”.

    3- I uncommented the code in my (child) functions.php and everything worked.

    So all good now.

    Thread Starter dccharron

    (@dccharron)

    Very kind of you to respond so quickly.

    I followed your documentation on how to filter spam with Akismet at http://contactform7.com/spam-filtering-with-akismet/

    I had split the author’s name as “First Name” and “Last Name” so I put the option “akismet:author” on each of them. Of course I put the “akismet:author_email” on the author’s email address field.

    So far so good. No spam has arrived for the past 30 minutes. Looks good.

    Thanks again.

    Thread Starter dccharron

    (@dccharron)

    No. It just started to work again after a few days.

    dccharron

    (@dccharron)

    @trailness Woo hoo! Added the code and emoji are gone! Many thanks.

    Still think it was silly to force them on everyone by putting them in the core.

    dccharron

    (@dccharron)

    @webliberty I agree with you.

    I assume that this change to the core is the cause of the following change to my website.

    I was using:

    to generate a purple left pointing arrow (solid triangle). That’s the character I found on w3schools.com which I use as a reference.

    After the upgrade, my purple arrow had been replaced by an image with a white triangle (pointing left) inside a blue box. How is that the same as a purple arrow?

    Fortunately, I discovered that by changing it to

    the problem is fixed. But I now have to go through hundreds of posts and pages on all my websites to see what unexpected characters are appearing instead of the ones I put there.

    @samuel Wood: I agree with @semrocc. The need to install a plugin to defeat core functionality seems, well, backwards. Shouldn’t it be the other way around? Shouldn’t the core provide the basic functionality and if you want emoji replacements, then install a plugin?

    Once everybody cools down and thinks rationally about this change I’m sure you will introduce Setting to opt in/out to emoji replacements.

    Thread Starter dccharron

    (@dccharron)

    I figured it out. Apparently I had not associated the specific page with the popup on popup edit screen. I’m sure I had ticked the correct boxes but I must not have “Updated” my changes. It’s working now so I can take this baby for a bit of a spin. Sorry for making any confusion I may have caused.

    dccharron

    (@dccharron)

    The problem with the

    Something has gotten mixed up!

    for me relates to sites that I have “moved”. If you then try to use the link:

    That used to be my URL for this site before I changed it. Update the WordPress.com Cloud's data to match my current settings.

    does nothing. I’ve tried it twice.

    So someone has obviously recognized that there was going to be some serious problems and provided a link to fix it but the link doesn’t work. Not sure who is responsible to fix that link. Is that WordPress 4.2 issue or a Jetpack?

    I’m beginning to think that Jetpack is a liability to all my sites and I should abandon it completely. I’d be happy to get other opinions.

    Thread Starter dccharron

    (@dccharron)

    Many thanks @nikeo.

    After upgrading to the latest version of your wonderful theme (3.3.9) I still experienced the entypo.eot 404’s but now that I’ve added the filter function you gave in that related topic I have not seen any more. I can now apply this to my other sites. Thank you so much. I have flagged this post as Resolved.

    Thread Starter dccharron

    (@dccharron)

    They don’t always come up. I might see one per day. The 404 monitor I use tells me that the browser that was used on this error was:

    Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)

    I read that to mean Firefox but am not sure if that’s correct.

    I’ve got other sites using Customizr and they all get the same error.

    Thread Starter dccharron

    (@dccharron)

    Yes. I still see the 404 for entypo fonts. The URL is

    http://haitidebeachresort.com/wp-content/themes/customizr/inc/assets/css/fonts/fonts/entypo.eot%29;src:url%28http:/haitidebeachresort.com/wp-content/themes/customizr/inc/assets/css/fonts/fonts/entypo.eot

    You can see in the URL that it is looking for a file belonging to the Customizr theme. I’ve checked to see if that file exists and it does.

    So I thought it might be a malformed URL but I’m no expert on all possible constructs of URLs (or should I say URIs). Perhaps it’s something I did but I can’t find it. I’ve just noticed something. I’ve got a hunch. I’ll post again if I think I’ve found it.

    Thread Starter dccharron

    (@dccharron)

    That’s a different issue. It’s related to Chrome generating an error when you don’t have chromecast installed. It’s really silly. Here’s the google group issue where that error has been discussed. I think Google have closed it but you’ll get the drift of the reason for the error.
    https://code.google.com/p/google-cast-sdk/issues/detail?id=309

Viewing 15 replies - 91 through 105 (of 154 total)