intowernet

Jordy,

It has been several weeks since I contacted you. Have you had a chance to look into this? We have several people who’s website is getting full of old pictures but they cannot clean the Media because they do not have Admin access and we cannot give it to them. This did not used to be a problem for them.

Thank you.

David

Jordy,

Thank you for responding.

Before the last update we had your plugin on several websites. It is there for other people who only had Editor roles, to periodically clean out old pictures. They could use it before and have used it. Now they cannot.

The option to access the Cleaner is available to them under “Media/Cleaner”. The dashboard come up for a second and then the API warning blocks the screen.

Here is something strange. I created a new user role (using User Role Editor) which was a duplicate of the Admin role but of course I had to give it a different name. Even the new user role cannot use the plugin.

Any suggestions would be appreciated.

Thank you.

Dave

Scott,

Thank you for getting back to me. This answers my question.

Is there a way to communicate with you privately? We are wanting to offer the pro version of this to many of our clients but I still have some concerns before we purchase several licenses for or customers. As I mentioned, I tried going through your website support and never got a reply.

Thanks.

Dave

That worked. Thank you!

Thanks for your swift reply!

Mrzpro,

I don’t know if this is the problem or not but a few of our websites displayed a message “This page didn’t load Google Maps correctly. See the JavaScript console for technical details” . It turns out that we were using a free trial of Google’s API keys and the trial was up. We had to upgrade to a paid plan in order to get the maps to come back up.

• This reply was modified 5 years, 1 month ago by intowernet.

We finally got most of our sites working by disabling both the “Contact Form 7” plugin and the “Really Simple CAPTCHA” plugin and then clearing the cache. The clearing of the cache was very important. On a few sites we had to revert back to an older version of Contact Form 7. I hope this helps someone.

We finally got most of our sites working by disabling both the “Contact Form 7” plugin and the “Really Simple CAPTCHA” plugin and then clearing the cache. The clearing of the cache was very important. On a few sites we had to revert back to an older version of Contact Form 7. I hope this helps someone.

We have a lot of sites that use this plugin and half are working and half are not. I reverted one of our most important back to the previous version and it is now working. On many of our sites it appears to be a Really Simple Captcha issue. Simply turning off the pulgin will not help as the code that is added to make the plugin work must also be removed.

Again this is not the issue on all our sites. I hope this helps someone track down the problem.

Marked as Resolved

Thank you for all your help.

Michael,

Thanks for responding and at least for giving me a direction to head.

Before I let you go could you answer one more question? Is there as maximum number of entries for the database? I just want to make sure that this is not what is causing the issue as there are a lot of entries in the database.

Thanks

The new update caused our site to crash. This is the second time this has happened since I have been using this plugin. Luckily after the first time I built another site simply to test the updates before updating it on the real site.

For those of you who have this problem, deactivating the plugin brings the site back up.

So what is the solution? Just leave it? During WP Installation I have no control on the prefix names. Do I delete the original fields?

Thanks for responding so quickly.

After fighting with this for 3 days now and deleting a site 6 times and re-installing WordPress (deleting databases, users etc) here is where I am at.

It appears that every time I created a clone from site A to a new site B the clone was adding the table fields from site A to the existing new site B. So I had two option fields, two user fields etc. but each had its own prefix. This was causing everything to link to the original site A. I created two new clean sites and used your development version. It is now working but there are still two sets of each field. This is not the way it worked in the past is it?

The servers where I am setting up the sites are on two different servers. The install on both servers is creating a prefix for both tables other than simply wp_ . Could this be the issue?