Josie Stauffer

That message is a warning, not an error, and should not have displayed unless you have set “WP_DEBUG_DISPLAY” in your wp-config.php file.

What it is warning about is something that, while it certainly ought to be fixed, should not have stopped your download. But thanks for making it clear that there was something missing in my testing setup — I should have caught it.

I’ve put out a new version with that particular problem fixed.

No promises, but I just released a new version and there are some changes around the way the download is implemented. It may possibly fix your issue, or produce a more useful error message.

You should be able to tell if the issue is a clash with another plugin by temporarily deactivating the plugin and trying your download again.

Sorry – it was needed to make the sorting work in the item mangement page. But a lot of hosting companies give you a choice of php version.

That sounds as if you may be running too old a version of php.

I’m afraid EntryWizard requires at least 5.3.0

Not at the moment, but both items are on my todo list.

The “headers already sent” message means that some output (probably a space or blank line) happened before it was supposed to.

Did you create an ewz-extra.php file? Or edit one of the other files? If so, check what you did very carefully. Make sure there is no ‘?>’ at the end of ewz-extra.php.

If not, perhaps you should first try downloading a fresh copy of entrywizard to make sure there is no file corruption. Then if the problem persists, let me know just which actions trigger it – is it just the one button, or all the download buttons? Does it happen at any other time?

That helps — the message is coming from the wordpress function that is used on the server to check the image dimensions.

There have been recent changes to the WP image handling code, so first, please check that you have an up-to-date version of WordPress.

The other difficulty with this function is that it’s behaviour can depend on which of two image handling packages is installed on your system. The more recent versions of WordPress default to ImageMagick if it is available, and if not, fall back on GD. You may want to ask your hosting company if ImageMagick is installed, since it is the better of the two. It would help to know which of these your wordpress installation is using.

That is the first I have heard of such an issue with EntryWizard, and I can’t reproduce it myself.
Can you tell me what software was used to create the progressive jpg?
And quote the exact error message received?

Thanks

I’m afraid that isn’t possible right now.

On Unix-type filesystems ( most websites are hosted on Unix/Linux ), filenames that contain spaces or punctuation require special handling, and are not normally used. Allowing them would make it much easier to introduce errors in the code.

I appreciate that Windows users may be used to different rules, and I may eventually add a facility to download ( but not store on the server ) files with less restrictive names. But that would take quite a lot of time, and I’m pretty busy right now.

If your aim is to have the titles display in a slideshow, you may want to try Flexishow (https://sourceforge.net/projects/flexishow/)

In version 1.2.4 I’ve added empty index files to all the entrywizard upload folders, plus a .htaccess file in the main one. I’ve also randomized the names of the downloaded files.

It’s a good point. I was trying to keep things as simple as possible and follow standard wordpress procedure for uploads.

It is fairly easy to protect folders, either with an empty index.php file in the folder, or with something like “Options All -Indexes” in your main .htaccess file. That stops anyone from getting a listing of the folder contents, although it does still allow anyone who knows the exact filename to view an image.

I’ll put it on my ever-growing todo list to see if there is a simple way to set an option that would stop direct access to the images.

Yes, so long as they are still on your server, and you have not deleted the webforms that were used to upload them.

Create a page or post containing ewz_followup shortcode, as described at the very top of the webforms page, and direct your user there.

You are lucky, because this is a fairly simple change and I was just about to release a new version anyway!

I’ll change it so it just logs the unrecognised field.

Should be out soon.

The html as displayed by the wordpress editor would be something like:

send an email to Joe Blow ([email protected])