Same issue here. Running WP 4.7.2
What browser are you using? We were having trouble with PDF replacement in Chrome, but it was working in IE.
We’re having a similar problem where we’re not getting an error message, rather the PDF replacement appears to process OK only to have the original file remain.
WP is up to date (4.7.2 Sparkling Banner theme). Getting same result on Chrome, IE, Safari and Firefox.
Hi
Similar issue as @steveattb – the file is upload but nothing updates in terms of published links resulting in 404 messages
Cheers and thanks in advance
-
This reply was modified 9 years, 2 months ago by
bob7t.
In almost all cases of a failure to replace a file, the issue is one of the following:
Case A: The file _is_ actually replaced as it should, but a browser cache makes it look like the file is not replaced. Solution: Clear browser cache or try in another browser/computer that has not previously accessed the file.
Case B: The original file on the server (the file you want to replace) has wrong file permissions, and the web server does not have permission to delete the file. Solution: Make sure web server user on server (usually ‘www-data’ on a Linux system) has permissions to delete the file.
Case C: The web server user on the server does not have permission to write to the uploads folder. Solution: Make sure web server user on server (usually ‘www-data’ on a Linux system) has permissions to write to the uploads folder.
@mungobbq thanks for your reply – why would this permission setting issue be limited to just one file type i.e. pdfs? and not every other file type or permission (read, write, execute)
@bob7t I can’t answer that. Did you get a chance to look at the error logs from your web server or in any other way get more details about the error?
It’s very unlikely that this is a problem with the plugin, since it works flawlessly on thousands of installations, but it’s of course possible. But without more details, I can’t tell you what could be wrong.
here’s the only error log
[Thu Mar 02 14:20:08 2017] [emerg] [client 81.179.236.110] (22)Invalid argument: mod_fcgid: can’t lock process table in pid 846239, referer:
Thanks for your response, Mans.
I have Administrator permissions without restriction on the site and have ruled out a caching issue by testing on other PCs in the office. Unfortunately none of these seem to be the problem. Any thoughts?
Cheers
Steve
Steve, it’s not the permissions in WordPress that matter, but the file permissions on the server.
Without a Web server error log there is not much more I can do to help.
Hi Mans. Thanks, am looking into it further. I’ve been advised to ask you if it has been tested on PHP7?
It’s def an issue with pdfs not updating – for our site it’s only one pdf per page, set as a download link from a button in Visual Composer – as a fix we’ve added a code block referring to the pdf from the media library e.g. [pdf-fix id=”1454″][/pdf-fix]
Hopefully this will work in combination with the plugin as it stands when replacing an existing pdf albeit that the shortcode has to be bespoke to each pdf on each page.
-
This reply was modified 9 years, 2 months ago by bob7t.
Yes, the plugin is tested fine with PHP 7.
@bob7t No, this sounds strange. Can you verify on the server whether the file is replaced in the file system?
The new pdf file is added to the ‘old’ folder alongside the old to be replaced pdf but no further update of the link is performed so we end up with a 404 when the link is clicked in the live site
Hi all,
Resolved!
WordPress appears to be erroneously enforcing file size limits in some strange ways which make it look as though there is a problem with the plug-in. In the host control panel, increase the maximum file size you can upload in the php.ini. Did this for both our company’s sites and both are working fine now.
Although my hosting was set to 64MB, WordPress was limiting my uploads to 2MB and identifying my file as being too large despite it being only 1.7MB. In Chrome it showed as being successful though, which made me think it was the plugin. It was when I tried in IE I got a message advising the file was too large (or so it thought) and thus the file wasn’t being replaced.
Plugin itself is still as terrific as always.
