PHP Warnings

  • JK

    (@justin_k)


    13 years, 4 months ago

    Two unique PHP warnings that are appearing from Wordbooker 2.1.25:

    [07-Jan-2013 09:11:44] WordPress database error Unknown column ‘fb_user_id’ in ‘field list’ for query INSERT INTO wp_wordbooker_postcomments (fb_post_id,comment_timestamp,wp_post_id,blog_id,user_id,fb_user_id,fb_target_id) VALUES (“3309143_10101343207408414”,1357549904,22703,1,1,3309143,3309143) made by edit_post, wp_update_post, wp_insert_post, wp_transition_post_status, do_action(‘transition_post_status’), call_user_func_array, wordbooker_process_post_data, wordbooker_publish, wordbooker_publish_action, wordbooker_fbclient_publishaction, wordbooker_wall_post, wordbooker_store_post_result

    and

    [09-Jan-2013 02:00:26] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘ 1
    , 80
    )’ at line 15 for query INSERT INTO wp_wordbooker_errorlogs (
    user_id
    , method
    , error_code
    , error_msg
    , post_id
    , blog_id
    , diag_level
    ) VALUES (
    1
    , ‘Looking for addthis.com in http://media.justin-klein.com/post-images/2013/23410-sim-cards.jpg’
    , 1
    , ‘ ‘
    ,
    , 1
    , 80
    ) made by do_action_ref_array, call_user_func_array, check_and_publish_future_post, wp_publish_post, wp_update_post, wp_insert_post, wp_transition_post_status, do_action(‘transition_post_status’), call_user_func_array, wordbooker_process_post_data, wordbooker_publish, wordbooker_publish_action, wordbooker_fbclient_publishaction, wordbooker_return_images, wordbooker_strip_images, wordbooker_debugger

    http://wordpress.org/extend/plugins/wordbooker/

Viewing 11 replies - 16 through 26 (of 26 total)
1 2
  • Thread Starter JK

    (@justin_k)

    13 years, 4 months ago

    >>Version 2.0 has, like most other WordPress plugins, no need to be de-activated for upgrading.

    …Right, but nevertheless it does seem like it should be able to *handle* deactivating and reactivating, don’t you think? šŸ˜› In particular, I deactivated it because I was upgrading WordPress. Then after updating wordpress, I uploaded the newer version and activated it. I didn’t assume it’d be necessary to reactivate the old version in order to update…

    >>OR there might be a fix..

    Hmm, but are we confident that wouldn’t mess up whatever Relevanssi is trying to do? Perhaps we should submit a topic to Mikko again, that this is still an issue introduced by his plugin?

    Plugin Author Steve

    (@steveatty)

    13 years, 4 months ago

    The problem is that you disabled it, upgraded WordPress, then replaced Wordbooker without re-activating it first… I can put more codding checks in place but that is what caused it.

    I’ve raised it with Mikko – just pointing out that replacing a global object with a stored version of itself is not really acceptable. Looking at the code I can’t even see why he does it – that code should not need the global post object and he doesn’t actually change anything in it as far as I can see.

    The problem is that reproducing it on my system is just about impossible which is why I suggested removing the $post from the list of globals in that code.

    Thread Starter JK

    (@justin_k)

    13 years, 4 months ago

    >>Mikko

    Yeah, I hear where you’re coming from. Hopefully he gets back and says it’s fine to just cut it, but it’s always risky to mess too much in other people’s code – especially if it isn’t “standards-compliant” and is as extensive as his.

    >> I can put more codding checks in place but that is what caused it.

    Forgive me if this is an oversimplification, but wouldn’t it be easiest to just check the current structure of the table, the expected structure of the table, and if they don’t match…it’s a clear sign that something is wrong? Even if all it does is to say “Oops – your schema is out of sync! Please check table (so-and-so),” it’ll prevent unexpected issues like this from arising under *any* circumstances.

    >>The problem is that you disabled it, upgraded WordPress, then replaced Wordbooker without re-activating it first…

    I disabled Wordbooker, removed Wordbooker, upgraded WordPress, and some time later, I installed Wordbooker again – the most current version. I never would’ve thought that I’d need to re-install an outdated version first, in order to subsequently install the current version….

    Plugin Author Steve

    (@steveatty)

    13 years, 4 months ago

    That’s what the schema verify code did and it was elegant and neat and very reliable but some people seem to have partially broken MySQL databases or are running on servers which are basically running a huge number of databases in one MySQL instance (usually cheap shared hosting) so my code which uses the MySQL Information_Schema hung. So if I want to use it I’ve got to recode things… which I might do…

    Thread Starter JK

    (@justin_k)

    13 years, 4 months ago

    Gotcha.

    Plugin Author Steve

    (@steveatty)

    13 years, 4 months ago

    If want you can comment out the line causing the error in wordbooker.php – its in the wordbooker_strip_images function:

    f ($flag==1) {wordbooker_debugger("Looking for ".$strip_domain." in ".$single," ",$post->ID,80) ;}

    But that might just move the message to the next debug if there is a problem.

    Thread Starter JK

    (@justin_k)

    13 years, 4 months ago

    I’d rather just hang tight for Mikko’s response for now, and get a proper/permanent solution. Wordbooker’s functinality seems to be working uninhibited, so it at least superficially looks like it’s just a matter of getting rid of error_logs in the interrim.

    Plugin Author Steve

    (@steveatty)

    13 years, 3 months ago

    He says that he is doing nothing wrong. Can you try turning off his plugin and seeing if the problem still occurs.

    Thread Starter JK

    (@justin_k)

    13 years, 3 months ago

    Hmm…well, I tried re-publishing with Wordbooker in testmode (and Relevnssi still active, just as a baseline test), and the error_log did not appear. It would therefore seem like I need to do an actual publish to test this. I’ll give it a try the next time I publish a post, hopefully in a week or so.

    Plugin Author Steve

    (@steveatty)

    13 years, 3 months ago

    I suspect that if the post has already been published then relevenssi will ignore the post.

    Thread Starter JK

    (@justin_k)

    13 years, 3 months ago

    Ah yeah, that would make sense.

Viewing 11 replies - 16 through 26 (of 26 total)
1 2

The topic ‘PHP Warnings’ is closed to new replies.