Support » Plugin: Post By Email » Fatal error: Call to undefined function wp_slash()

  • Resolved Thorstein

    (@thorstein)


    At first it worked…then:
    ( ! ) SCREAM: Error suppression ignored for
    ( ! ) Fatal error: Call to undefined function wp_slash() in C:\wamp\www\pop\wp-content\plugins\post-by-email\class-post-by-email.php on line 384
    Call Stack
    # Time Memory Function Location
    1 0.0011 162072 {main}( ) ..\tools.php:0
    2 0.0022 205000 require_once( ‘C:\wamp\www\pop\wp-admin\admin.php’ ) ..\tools.php:10
    3 0.4013 14938384 do_action( ) ..\admin.php:111
    4 0.4360 14980224 call_user_func_array ( ) ..\plugin.php:406
    5 0.4360 14980240 Post_By_Email_Admin->maybe_check_mail( ) ..\plugin.php:406
    6 0.4361 14980312 do_action( ) ..\class-post-by-email-admin.php:93
    7 0.4361 14981200 call_user_func_array ( ) ..\plugin.php:406
    8 0.4361 14981216 Post_By_Email->manual_check_email( ) ..\plugin.php:406
    9 0.4954 14987832 Post_By_Email->check_email( ) ..\class-post-by-email.php:209

    Here’s my Activity Log:

    October 27, 2013, 10:49 am An error occurred: Error connecting to mail server.
    October 27, 2013, 10:41 am An error occurred: Error connecting to mail server.
    October 27, 2013, 10:28 am An error occurred: Error connecting to mail server.
    October 27, 2013, 10:12 am Please wait 5 mins to check mail again!
    October 27, 2013, 10:04 am Please wait 5 mins to check mail again!
    October 27, 2013, 10:04 am Please wait 5 mins to check mail again!
    October 27, 2013, 10:02 am There doesn’t seem to be any new mail.
    October 27, 2013, 9:58 am Found 1 new message.
    “Test post by email” failed PIN authentication; discarding.

    Reading from the bottom up:
    9:58 Seemed to work on POP3 110 but I stupidly entered [pin=1234] instead of [pin 1234]. Should I have put [pin &*^4332] in the email after hitting “Generate”??

    10:02 didn’t realize that POP3 retrieval deleted the file from my inbox, so this looks like it was ok.

    10:04 Why try my patience like this?

    10:08 (or thereabouts) I hit the above fatal error. Changed to IMAP started trying with and without SSL. Still fatal errors. I probably could have found an IMAP configuration that could have worked, but having to wait 5 mins between each tweak, I finally gave up and uninstalled.

    11:00 Reinstalled to vanilla POP3. DB settings were preserved, got the same fatal error. Perhaps something bad is stuck in my DB?

    http://wordpress.org/plugins/post-by-email/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Whoops! IMAP didn’t generate Fatal Errors; I just couldn’t configure it to connect. I use an off-brand mail server (Ability), so don’t waste too much time worrying about the IMAP failures.

    Plugin Author Kat Hagan

    (@codebykat)

    Hi,

    What version of WordPress are you on? wp_slash should work as far back as 3.6.

    As for “why try your patience”, the five minute delay is supposed to prevent you from accidentally DDoSing your mail server. If you enable WP_DEBUG, it will allow you to check as often as you want. 🙂

    I’m not sure I understand your question about PIN authentication. The format is “[pin ####]” where #### is whatever you’ve saved in your options. If you use “generate”, it just fills out the field for you; you still have to save your settings to update it.

    Thanks Kat,

    I’m in 3.6.
    Thanks for the WP_DEBUG tip.
    Ah!, I thought “generate” was like “generate an SSL key”…I suppose I would have figured out it means “Generate a random PIN” soon enough if I had had WP_DEBUG on.

    Plugin Author Kat Hagan

    (@codebykat)

    Huh. That’s super weird, the Codex says that wp_slash was introduced in 3.6.0. Lemme spin up a test version on 3.6 and see if I can duplicate that error. The other possibility is that somehow the file is being called without including all the WP functions, which… I don’t even.

    Plugin Author Kat Hagan

    (@codebykat)

    Hmm. It does work for me on 3.6. Just for the sake of argument, can you open up your wp-includes/formatting.php and see if the wp_slash function is there?

    Sorry, Kat!

    Turns out I was running 3.5.1 on this site :-/. I guess it’s time to upgrade!

    Plugin Author Kat Hagan

    (@codebykat)

    Ah, yeah — especially since 3.7 just came out!

    I’m marking this as resolved since the plugin is currently only supported in WP 3.6 or higher. I might go back and try to add support for older WP versions someday, but that’s not a super high priority.

    Please let me know if things still don’t work properly after upgrading!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Fatal error: Call to undefined function wp_slash()’ is closed to new replies.