NetzzJD

Yes, we use WP as a CMS and have different level user roles for our clients to edit in the backend/dashboard. We do not want public or random users to add or access jobs or be able to create new jobs; just to be able to see and apply to them. We use it as our “Careers” page and only list internal job openings that we control. In this case, I do not want to open up certain users as an Admin just to be able to fully access the backend of WP Job Manager.

I actually kept digging/testing and now just use the User Role Editor plugin to manually allow Editor role to use this plugin fully. Thanks for the response!

Yes, thank you. I just ran that tool today as well. I now have the setting to save the past year only versus all statistics data. The Reset Statistics button ran just fine for me within a few seconds and did seem to actually delete the correct old date records from the table. Mine went from 1 million rows to 500k at least. And I do think the records are legit impressions and clicks for all the ads. It just seems that this tool still needs to be run manually though and is not an automatic action unfortunately. I also wish I could look back at all ads run to get historical data without deleting the records altogether.

I also have recently been seeing the slowness described on all the admin Ad Places pages too. Takes about 30+ seconds to load each time.

So far it’s only been when opening a new Event Espresso page or editing an existing EE page. I can contact them about it as well; however, the file being flagged and stopping execution of the rest of the page is this EDD plugin. Any further info I should let the other developers know? Specific function or JS call causing the error?

There are not any caching plugins installed at all nor does the server have anything cache related.

It is specifically preventing pages from the Event Espresso plugin from working correctly, although EDD is the only error appearing in the console, stopping other JS functions like date pickers and even WP’s core permalink options to appear.

It was previously running (and working correctly) under WP 4.5.4.