Forum Replies Created

Viewing 8 replies - 61 through 68 (of 68 total)
  • Thread Starter J.D. Grimes

    (@jd55)

    Okay, I did that. I haven’t seen the error again yet, but like I said, it only happens a few times a day when the server runs wp-cron.php. I guess I have to just wait and see? Or could I try to test wp-cron somehow?

    Thanks for your help so far.

    Thread Starter J.D. Grimes

    (@jd55)

    Okay, I am still getting the errors.

    Thread Starter J.D. Grimes

    (@jd55)

    Okay, activated 2012 theme, deactivated all plugins. Now do I just have to wait to see if I get the error, or can I run wp-cron somehow to test it? It only happens a few times a day.

    Thread Starter J.D. Grimes

    (@jd55)

    Okay, I decided to move to a different plugin, but the messages were still garbled. My website is set up to use UTF-8 encoding, and to fix this I had to set the mb_* encoding overload to 6 instead 7. In other words, the mail() function wasn’t working right with UTF-8 encoding.

    So now this is fixed!

    Thread Starter J.D. Grimes

    (@jd55)

    Another update:

    I no longer think that this error is related to my problem. It has to do only with one of the add-ons, which I am not using right now.

    The errors that I posted above are output after the mail is logged. Here are some errors that it puts out before logging the mail:

    2012-10-18 10:54:25 000000 -- PHP [E_NOTICE] 8 : Trying to get property of non-object in /home/efield5/public_html/wp-includes/post-template.php at line 30
    2012-10-18 10:54:25 000000 -- PHP [E_STRICT] 2048 : Non-static method nggGallery::get_option() should not be called statically, assuming $this from incompatible context in /home/efield5/public_html/wp-content/plugins/nextgen-gallery/lib/shortcodes.php at line 47
    2012-10-18 10:54:25 000000 -- PHP [E_STRICT] 2048 : call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::the_content() should not be called statically in /home/efield5/public_html/wp-includes/plugin.php at line 170
    2012-10-18 10:54:25 000000 -- PHP [E_STRICT] 2048 : Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /home/efield5/public_html/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php at line 1282

    I don’t have the time or know-how to track down these errors. ??

    Also, I said above that the email preview worked fine. Well, that’s only partly true. The email preview shows the theme and email title, but it doesn’t show any of the actual email text. The same is true if you try to view the email in your browser from the link — there isn’t any of you message there, just the theme with the email title.

    I am still trying to figure this out, but I don’t know enough about how the plugin works to know what might be causing this.

    Thread Starter J.D. Grimes

    (@jd55)

    This is just an update. The problem is still the same, and when I tried subscribing, the confirmation email was also just garbled. It seems that this plugin is incompatible with PHP 5.4, as evidenced by this fatal error.

    When that is “fixed” so that the PHP can execute the code, then you get these errors in MailPress’s logs each time it tries to send out a message:

    2012-10-11 17:10:47 000000 -- PHP [E_WARNING] 2 : mysql_num_fields() expects parameter 1 to be resource, boolean given in /home/efield5/public_html/wp-includes/wp-db.php at line 1121
    2012-10-11 17:10:47 000000 -- PHP [E_WARNING] 2 : mysql_fetch_object(): supplied argument is not a valid MySQL result resource in /home/efield5/public_html/wp-includes/wp-db.php at line 1126
    2012-10-11 17:10:47 000000 -- PHP [E_WARNING] 2 : mysql_free_result() expects parameter 1 to be resource, boolean given in /home/efield5/public_html/wp-includes/wp-db.php at line 1131

    I don’t know how to fix this so that the plugin will work right with PHP 5.4. I was hoping that maybe Andre could at least point me in the right direction.

    Thread Starter J.D. Grimes

    (@jd55)

    Thank you for the reply, Donncha. I am going to set up a test and see if it works.

    Thread Starter J.D. Grimes

    (@jd55)

    Thank you for your reply, Max. I just tried your suggestion and got a 401 error. I found out that the problem was that I had blocked any URL request from the server with “select” in it in my .htaccess file. The file is q2w3_get.php?width=640&height=485&action=q2w3_table_wp_page_select&id=inc_pages_select….., so it was being blocked. Next time something like this happens I will be sure to double check if it is something like this.

Viewing 8 replies - 61 through 68 (of 68 total)