phikai

Josh, Any chance you’ll be releasing that script?

I’ll admit that my technical understanding of this isn’t clear… but it does seem to eliminate that Notice.

Unfortunately, you won’t be able to use the plugin without getting your hosting provider to upgrade to at least PHP 5.3. That’s the minimum required version for this function to work properly. That’s also why you’re not seeing any posts automatically as it’s failing silently when trying to use this.

This should be resolved with the 1.2.8 release which moved away from git submodules and directly includes the needed repositories. This makes it easier to push the updates the wp.org repositories moving forward.

It looks like it was a caching issue on our end. When we updated to 3.4 for some reason it was still looking for the includes file. Purging the caches and then activating the plugin worked for us.

Thanks for the awesome support!

When was it removed? I’m wondering if it’s a caching issue on our hosting setup that’s still asking for it… was it in version 3.3?

Ok… so updating to WP 3.3 seems to fix the issue with YARPP 3.4 throwing a fatal error. Not sure if this is intended to break the backwards compatibility, but that’s what I’m seeing.

I should note that I downloaded the plugin from the admin interface after deleting the existing one. It won’t activate because of that error.

I have the same issue on another site (also with ZippyKid… who I work for actually). It seems the plugin download doesn’t have the includes.php file and so the require_once is throwing a fatal error.

Warning: require_once(/home/XXX/websites/XXX/htdocs/wp-content/plugins/yet-another-related-posts-plugin/includes.php): failed to open stream: No such file or directory in /home/XXX/websites/XXX/htdocs/wp-content/plugins/yet-another-related-posts-plugin/yarpp.php on line 15 Fatal error: require_once(): Failed opening required ‘/home/XXX/websites/XXX/htdocs/wp-content/plugins/yet-another-related-posts-plugin/includes.php’ (include_path=’.:/usr/share/php:/usr/share/pear’) in /home/XXX/websites/XXX/htdocs/wp-content/plugins/yet-another-related-posts-plugin/yarpp.php on line 15

Where does this file come from?