[Plugin: The Events Calendar] no "Events", "Add Event" or "Categories"

Hi there mintunath. Thanks for the note here, and for reporting this. This is an odd issue. Can you confirm that you’re running on WordPress 3.4.2, and that this still occurs even when deactivating all other plugins and reverting to the default Twenty Eleven theme? We’ll do what we can to troubleshoot from there.

Hi again mintunath. How are you doing? Are you still having issues on this end, or did you get the topic sorted? Want to double check before I mark this thread as RESOLVED. Please let me know so we can follow-up as needed on our end. Cheers!

I’ve just installed your plugin for the events calendar.

I don’t see a calendar on my Events page and I don’t see any feature to ‘add an event’.

vwat.org/events

Sandra Healy
[ redacted, support is offered via the forum and not email ]

Hi,
I am having the same issue.
I think I have isolated it to a clash with Advanced Access Manager.
I have set up testone.oandb.info
Admin: test P-word: event

If you deactivate Advance Access Manager then the correct Events dashboard appears. Reactive Advance Access Manager and the Events menu is only partially there.

Very keen to get this working and looking forward to upgrading for several client sites I am working on.
cheers
Graham
[ redacted, support is offered via the forum and not email ]

Further to above…

Advance Access Manager [AAM] allows control of capabilities. There are a bunch of capabilities showing associated with events Calendar. If you deselect these, save, then re-select then and save the Events menu appears to be restored.

So, it might be a capability issue. I tried this on my production site, but it did not have the same effect.

Hoping this is a simple issue.
Graham

Hi folks. Thanks for the follow-ups here.

Sanhealy: are you still having issues? My guess is that this has to do with the fact that permalinks aren’t enabled on the site; make sure to set a structure like /%postname%/ and let me know if the issue persists.

Graham Stacey: interesting; that’s the first we’ve heard of this clash but it is definitely possible that there’s an issue here with that plugin. (I would recommend bringing this issue up to their devs as well, just to be safe). Am I reading your note correctly in assuming you found a workaround, though?

This thread has been inactive for a couple weeks now, so I’m going to take the liberty of marking it Resolved. Let me know if anyone disagrees.