R1Law

Great! The other plug in breaks under 7.0 but reverting back to 5.6 “fixed,” not a good solution so I’ll be migrating to this.

I’m getting the same response from my host (A2 Hosting). Patchman is throwing the flag based on phpBB. Everything seems to key on javascript (inc.libs.js.php). As of yesterday (11/14) the issue on Patchman service has been marked as retracted, which means: The detection has been resolved, because the file was changed (outside of Patchman) or has been removed. Most likely the end user has updated his CMS to a newer version.

I did not intervene so this was driven by a system update or java update.

Depending on your host account, you can typically find the PHP version under software or software and services. Look for PHP Version and select the either the system default or version 5.3.xx (5.3.29 on my host).

I had the same issue and my hosting account runs PHP 5.3.29. Just an FYI – I reset the plugin to version 1.7.32 and run without issues.

I’m hazarding a guess. If you’re working on a live website (please try local sites for new plugins, updates, etc.) then you’re also likely view a cached version of your pages. This is especially true if you have services like Cloudflare, etc. The “now it seem [sic] work” is indicative of the type of delay you’d get with Cloudflare not toggled to develop mode. Just something to think about.

@buzztone – THANK YOU regarding the tip on required field [email* your-recipient] The form had been throwing this error on a field with multiple selections in a dropdown (including blank), it’s easy to overlook the simple solution.

Well…while gathering the files to move to manual update…it process seems to have resolved itself – for some reason the update just seemed to be taking an extraordinarily long time to complete. Some observations
– the dashboard became active but with the message that the automatic wp update had failed.
– during this time there was a 15/20 minute delay on my side working to backup database and gather file info..
– after returning to site and refreshing it showed that the update had installed and that WP 4.2.2 was running.

Issue resolved – by itself. Strange, but good.

Reversal of opinion here. Apparently the bundle download contained the version one files, I subsequently received an email with the two different versions and uploaded the version 2.2 compatible files. Plugin is now working as advertised. I feel as if this is an issue with different version on different purchase channels. Developer cleared this up and rating is now a 5 based on it doing exactly what I wanted it to do!

I was only able to download one…how do I download the correct version?

Sorry,
Just frustration with what should be a simple issue….

I’ve rezipped the files downloaded from Evanto and it is installed. However the template bundle installs but is not recognized by the plugin…The photo vote is exactly what I’m looking for so I’d love to get that working…

What I see after uploading the template zip is that something has been installed but it is labeled as unrecognized and has no author or version number associated with it…

To be clear, I’m reviewing the PRO version…

Opps, that’s been added – sorry. Marked as resolved.

Just saw the update jumped in…fastest fix ever! (good timing).

Here’s the issue: Doing development with password autofill is a bad thing….

For some reason the auto fill in Safari takes the Server port and the password in the Postie setup page and over-writes the correct information with field data that is NOT the correct port number – it looked like it was filling in the port box with the site title, but not sure. Stranger still is that the port number field looks like the correct information in the database on the server side (can’t figure that one out).

Regardless, we discovered this through running the full debug report. I will email you a full copy of the correspondence with the hosting provider. It’s a run with the error and one without (the one without was after uninstalling Postie, and then reinstalling, configuring, and immediately testing). The error was cropping up after the test when the Safari behavior overwrote the correct port number.

When attempting to use POP3-SSL this generates:
Warning: imap_open() [function.imap-open]: Couldn’t open stream {mail.xxxxxxx.com:xxxxxx/service=pop3/ssl/notls/novalidate-cert} in /home/xxxxxxx/public_html/xxxxxxx.com/wp-content/plugins/postie/postieIMAP.php on line 89