• Resolved siliconsara

    (@siliconsara)


    I first registered this error (as seen here) with woothemes since I switched themes to Twenty Ten on a test, and it worked, everything returned, so I thought it was a theme problem.

    So, I reported the error with woothemes and they are now telling me that it’s a problem with this plugin.

    So, here I am. Any ideas on what’s going on? Currently using all recent and up-to-date versions, both the plugin and wordpress.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Dutch van Andel

    (@veraxus)

    The first error seems to indicate that one of PSC’s deprecated theme functions is being used. Since that file is being deleted for the next version anyway, you can safely do this to fix it:

    1. Open this file in a text editor: /wp-content/plugins/contexture-page-security/contexture-page-security.php
    2. Near the very bottom of the file (line 131), you’ll see this line:
      require_once 'controllers/theme-functions.php';
      Delete that line.
    3. Save and/or upload the modified contexture-page-security.php file.

    That’s it. If you get a different error after that, you’ll probably need to remove a function call from your theme as well. I simply deprecated the original theme functions to give developers a head start in switching over to the new class-based ones.

    I should also point out that the second and third errors refer to a plugin called ‘wassup’; only the first one referred to PSC. So you may want to see whats up with that plugin as well. ??

    Thread Starter siliconsara

    (@siliconsara)

    This did the trick! I did get another error when I followed your instructions and replaced the function call with CTXPS_Queries::check_protection().

    Thank you for your help!

    PS, the wassup error was also fixed.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘call to undefined function check_plain()’ is closed to new replies.