Support » Plugin: SmartPost Templates » Does not work with WP 3.9.1

  • Resolved Adrian Badarau

    (@adrian-badarau)


    Hello,

    I am having a problem using the latest version in WP 3.9 I get a require error:

    Fatal error: require_once() [function.require]: Failed opening required ‘ajax/sp_postAttachmentsAJAX.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/seomark/public_html/wp-content/plugins/smartpost-templates/components/attachments/sp_postAttachments.php on line 39

    I have checked and all the files are on the computer in the respective directories.

    Also would be much appreciated if the wysiwyg editor for the text could be made smaller or hidden because you can’t see the text and type.

    https://wordpress.org/plugins/smartpost-templates/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Rafiki

    (@rafdizzle86)

    I am planning on adding an option that allows you to turn CKEditor on or off.

    As far as the required_once() error, I just tested the plugin on WP3.9.1 and could not replicate the error. I think it may be a PHP version issue and/or configuration issue – i.e. your PHP configuration doesn’t like using relative paths (see this artcile).

    So, if you want to test a quick fix, try to change the code to require_once(dirname(__FILE__) . 'ajax/sp_postAttachmentsAJAX.php' ).

    I will push out a patch which will replace all the require_once() calls prefixed with dirname() ASAP!

    Thanks for the feedback!

    Plugin Author Rafiki

    (@rafdizzle86)

    I just updated the plugin with the fix, let me know if you’re still having trouble!

    This line 39:

    require_once( dirname( __FILE__ ) . ‘/ajax/sp_postAttachmentsAJAX.php’);

    is causing a fatal error because the file name in the ajax directory is
    slightly misnamed, here is the original file name:

    sp_postattachmentsAJAX.php

    You need to rename that file in the distro package and capitalzie the word attachments so it is like this:

    sp_postAttachmentsAJAX.php

    Plugin Author Rafiki

    (@rafdizzle86)

    @rkcook: Yep, that was the issue! Most recent version should have that fixed.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Does not work with WP 3.9.1’ is closed to new replies.