If I am signed in as admin or contributor, both which have full rights to scheduler events, I have no problems.
If I am not signed into Wordpress and access the Scheduler (calendar) page as a “guest”, I get a LoadXML - Incorrect XML error pop up and the calendar is blank.
The guest does have View privileges to the calendar through the Scheduler admin.
Any ideas on how to resolve this?
Much thanks in advance!
OK, I’ve got one more clue. Seems like this is a permission error problem implicating the following piece of code in dhtmlxscheduler.js
this.xmlDoc.open(B?“POST”:“GET”,C,this.async);
Any thoughts on how to overcome this?
Once again, this only happens when the user is not logged onto wordpress … it’s only happening for “guest” users.
Sorry for the piece meal trickle of clues … but here is another one …
It turns out you don’t actually have to log in as admin or contributor to avoid the error … you just have to go to the login page (…/wp-admin) … and without logging in, if you go back to the public/guest calendar, it works! So, if you go directly to the calendar, you get the permission error and it doesn’t load the calendar events, but if you go to the wp-admin login page and then go to the calendar, it avoids the permission error???
Check the http paths for the page where scheduler works and where it shows an error - are both path have exactly the same domain or it differs a bit ?
Stanislav, you nailed it! Thank you!
There is a switch in the domain name, both resolve to same site/files, but one has the word “the” in front of it, and the other doesn’t.
So, I still don’t understand where it’s breaking and how I can get it to work with both versions of the URL/domain? Is this a cookie domain path issue, or a Wordpress setup issue, or something else?
For example, I want it to work with both these URLs
www.thefoo.com
AND
Right now, it only works with one of those.
I guess I can redirect it to the URL that works, but I’d rather understand what is breaking it and try to make it work with both without having to redirect.
Thank you again!
As for now , plugin can work correctly only if you are loading page from the same domain as specified in WP configuration.
We are preparing update, which will remove this limitation ( probably will be available in few days )