cbonallo

Also, two reports of Import using up all resources and sites going down temporarily.

We will have to disagree. If I run your Import the program breaks. That is reality. Does this before I can deactivate Memphis Docs. Your program delete .htaccess file so responsible for system reaction. Simple.

Oh, yes I do. But design has to meet reality. These sites ae in production. Memphis Docs is Network Activated. I cannot deactivate the Memhpis Docs plug-in until all 20+ websites are done doing the import, creating new WP Docs pages, one at a time, on their own time table. I gave them a reasonable time frame, 30 days to make the changes. Again, if another program is putting the .htaccess file back then it would not do that if you don’t delete it, but, instead modify it. I know because none of my modified .htaccess files have been changed.

• This reply was modified 1 year, 3 months ago by cbonallo.

I can only report what is happening. If you are deleting the file then something is putting it back immediately. Deactivating the Memphis docs plug-in would not change that and is impractical since every site has to do the import and I cannot force them to do it instantly.

It appears the system is reacting to the deletion of the .htaccess file. Could you not just replace it with Options +Indexes as the only content? Would that fix this issue?

I can only tell you what happened. In test we reported the issue after trying the import. In production, I was proactive to avoid the access errror. Steps I took are as follows:

1. I went into each sites mdocs folder and modified the .htcaccess file and replaced the Deny access all command with the filtered php version I shared with you.
2. I did this for every site in our network.
3. I then ran the WP Docs Import on the main site and found the error
4. I then opened the previously modified .htcaccess file and the Deny access all command was back; which I reported to you. So I modified the file again, but it still gave the error when accessing files. You said to contact my hosting support, so I did.
5. They discovered that the permission to read the .htcaccess file were also altered and were now 660. Once they changed those permissions back to 644 the error went away.
6. So I worked with another webmaster on another site and had them do the WP Docs Import. Same thing occurred.
7. I checked some of the other site that had not run the import yet and the .htcaccess file modifications I made were still there.
8. The I did it again on a test site and double checked just before and after the state of the .htcaccess file. Same thing happened.

So I am absolutely sure the file is getting changed when the WP Docs Import is ran. How and why it is occurring, I have no idea. That’s why I asked you to look into it. Could your code be triggering a directory reset? Triggering a malicious code protective response from the server? I am not a wordpress developer and have no clue.

• This reply was modified 1 year, 3 months ago by cbonallo.

Thanks for the quick fix! Awesome support.

No, they are not helpful.

We just upgraded and deployed to our production site using WP Docs and the access error is back even with the above fix that worked on our clone site. Any idea why? Please help!

Service Documents | Washington Northern Idaho Narcotics Anonymous (wnirna.org)

Thanks, that will work. Appreciate the quick response!

I’m new to Apache so the reasurance helps. Thanks for your time.

Cory

Thanks so much! I will take this back to my committee.

Thanks so much for the quik response. It refreshing! It was the .htcaccess file. This is what was in the mdocs folder:

(mdocs directory)

Deny from all

Options +Indexes

So I modified it to the same file permissions as the Uploads folder:

#Begin Really Simple Security

<Files *.php>

Require all denied

</Files>

#End Really Simple Security

Options +Indexes

That fixed the issue. Do you see any security risks in this change?

Again, Thanks for your support!

Then how come I get a this error?

Forbidden

You don’t have permission to access /wp-content/uploads/mdocs/01-22 RSC Minutes.pdf on this server.

You can use the link and try for yourself.