jospoika

I’ve found something – many hours later…. Okay… so the link for the above mentioned ” /wp-admin/ppma-authors” so far, only comes up once the plugin “Admin Menu Editor (Pro version) is activated. Thus, I’m assuming we’re not technically supposed to access this link?

The link does not appear after activating:

Contact Form 7
Advanced Custom Fields Pro
Business Manager
Knowledge Base for Documents and FAQs
MainWP Child (linked to MainWP Dashboard)
NextGen Gallery
Plugin Groups
PublishPress (Calendar, etc)
PublishPress Checklists
Publish Press Revisions
Publish Press Series
Really Simple SSL
The Events Calendar
UpdraftPlus
WooCOmmerce
WP Job Manager
WP Remote Users Sync

These were all installed and then PP Author link only appeared after installing the Admin Menu Editor Pro (link to ppma-authors).

Can you please confirm if this is supposed to happen? Are we supposed to access this link? I will keep going to see if I can find the plugin that created the Media Library and other issues (if I can find them… ?? )

Cheers
Jocelyn

p.s. Hope you don’t mind the multiple updates as I’m working through this (on the staging site for our non-profit organisation. I need to make sure everything works before going our members access the admin dashboard and before going public….

Hello again, so I’m still checking things through – and have come across (I hope) a minor error…

When selecting ‘Authors’ in the Dashboard Admin, the 1st menu option under Authors (as there is 2 of these?) one is taxonomy author, the top one is to /wp-admin/ppma-authors. The latter appears broken, causing a 404 page not found.

Any idea how to fix this? I have seen this error listed by another person, but there was no resolve published (at least not on the support thread I read dated over 2 years ago).

Cheers
Jocelyn

Hello Riza,

Thank you for your patience…. Ok… So some fantastic news, when all other plugins are deactivated, Publish Press Co-Authors… works as it always has! Phew! Great news for you… still frustrating for me.

I’m now on my 4th re-run of stepping through plugins, trying to find the mismatched culprit. So far, all plugins are working on their own accord so this is why I still think it could be simply a conflict between plugins – which ones – I do not know … yet. I’ve taken to re-activating the Publish Press plugins first and there’s no issues there at all. So, finding the conflict is the challenge. Thank you so much for your help so far, and again for your fast response time. After four re-runs of activating plugins, I am now 99.9% sure that PublishPress is not one of them. ?? I will keep persevering though…

Have an awesome day/night
Cheers
Jocelyn

I will go through the plugins again tomorrow and test that out. To be honest, I’ve not had this happen before either.

Thank you for your patience and understanding though!

Cheers
Jocelyn

Hi Riza,

Thank you for such a quick response, appreciate it.

Yes, this is only happening with your plugin. I have another co-author, multi-author plugin currently working (Molongui) with no errors loading the Media Library (yep – unusual :)). The problem is occurring over 13 newly created sites (not multisite) and the staging site for one. All sites are on the same hosting server, half of them are subdomains. The others have their own domain names. There’s no apparent issue with other PublishPress plugins. I’m still thinking it maybe a plugin conflict, but no idea which one at this time.

Cheers
Jocelyn

Hello Aurovrata,

Thank you for such a quick timely response – really appreciate it. It ‘was’ a fresh install with a number of plugins pre-installed that I had used before. I tried using different browsers, and upon hitting the ‘update’ the code continued to exit to the Posts menu. To be honest.. I gave up. I did manage to check out the PHP history. There were a number of warnings (like over 200) for non-active plugins, mainly the contact-form-7-paypal-add-on (only 4 for this one) and cf7-skins-innozilla (many warnings with this one). Both were not activated – so I’m not sure why there were so many errors. Nothing showed for any CF7 plugins.

I then ran a couple of the WordPress cleaner plugins – but these had no effect to fix the issue either. I totally gave up this point. Fully deleted wordpress and tables. I’m now running another fresh install! Good news, so far everything is working, I’ve managed to create a number of partial forms and have had no issue updating them. So I think the problem was definitely on my server side. But I do thank you so much for your replying to my request for help! Really appreciate it and I pray no further issues LOL

Do you do any custom work at all as I have a particular dynamic field that would make my team’s life really easy, and wondering at all if you can help (in regards to the Smart Grid and the Post My CF7 Form plugins) for a non-profit registered organisation?

I look forward to your response and again, thank you for your awesome support!=.

Cheers
Jocelyn

Hello Takayuki,

My apologies for the duplicate post – to be honest, I didn’t think (maybe stressing a little bit???) ??

Okay, I’ve found something interesting. The error as I initially documented above, occurred when using the Chrome browser.

I then installed another test server with a clean install of WP version 6.0 and the same thing happened. However, I’ve just ran both the clean install and the developing website on Firefox. Using Contact Form 7 and the Grid utility only, I’ve tried to re-create the problem.

First, I changed the email form tag to anything-email, then updated the mail tag for the corresponding form tag, saved the form, and.. bingo – it worked. And then it worked again. Maybe the issue is on my side – something to do with Chrome and cookies? I’m really not sure. If anyone finds that after changing form tags on both form and the mail tab – then saving the changes, whereafter the addon exits to the sidebar “Posts” link – I’d really like to hear from you. The more I think about it working in Firefox, the more I think the problem is definitely on my end.

Hope you don’t mind me updating this. Current solution – use Firefox. Will test again tomorrow with Chrome to see what happens. Will leave further feedback here, if still not working. Will also let you know if it is working on both environments – with same outcomes.

Cheers
Jocelyn