Output settings aren't saving

OK. Just found out the initial install of My Calendar seems to have created a page that I wasn’t aware of. I discovered it by digging into the wp-options table in the database.

So – find and delete the default calendar page reference THEN manually change the link to my new calendar page (mc_uri) AND change the page id (mc_uri_id).

I am having the exact same issue – where did you find the wp-options?

You need to go into the database – Using phpMyAdmin – and find the table wp_optionsThen search in the option_name column for entries starting in mc_ This screenshot should help.

https://www.rocklilydesign.com.au/MC_patabaseEdit.jpg

You need to find and edit mc_uri to the correct url AND page ID.

Thank you thank you!!! It worked!!!

That’s great. Glad to help.

Hi – I’m glad you both were able to get this solved, but I’m not actually at all certain why it would be happening. My Calendar does create a page on installation in some cases, but that should be apparent because it would show up in your list of Pages. Setting the default calendar page should be no problem; you should be able to define any site URL in that field, as long as it’s one that actually exists.

If either of you would be willing to submit a support request so I can try and follow up on the question of why, I’d appreciate it. (My Calendar > Help)

I have the same problem and would much prefer to use the Settings rather than mess around with the code.

I hope this can be resolved soon

If you can submit a support request, I’d greatly appreciate it. Nobody has yet submitted one on this issue, so I have no information to go on.

This appears to be related to situations where the page you’re using the calendar is protected – either because it’s in a member’s only section or because the entire site is protected. If anybody else in this thread can let me know if that’s true for them, I’d appreciate it. I’ve already got word from @ritch47golf

Joe – I can confirm my site is currently using Maintenance Mode plugin so that could be the issue – something preventing the update of that particular field/s in the database.

As I’ve fixed the issue, albeit in a roundabout fashion, I won’t be submitting a ticket. Others on this thread could.