I have reset al my permissions with no luck. I also found in console that there are some extra â//â in the HTML which if I remove in the browser I can click on the âadd relationshipâ button and get to next screen.
Question: Is this just me, or should I add as bug on Github?
I wouldnât say itâs a bug if it only happens in that particular installation. All it takes is a single wrong delimiter to get the screens to leak HTML like youâre seeing.
On your screenshot that part with the arrow seems correct to me (the delimiters are being escaped). The parts that seem wrong to me are these:
But you would need to find the file where those things are coming from, and it can be quite trickyâŚ
Hey I found the solution to this problem!!! Iâve been avoiding it for a while but if anyone else has it, I rebuilt and repaired all the JS files, grouping files, etc. in Admin/repair.
I had same exactly error issue, but clearing JS and setting perms didnât do anything.
So next step (whenever I have a major system crash)
I started deleting Vardefs in the custom modules (Not in The the Extension folder) being in developer mode you can get instant results when modifying these folders e.g.
It does Really have a Colon.
Great catch PGR, nice to have a fresh set of eyes.
Iâll make sure to let the owner of the plugin know so they can fix it on there end.
The installation that had the problem did indeed have a 2 factor id plugin that uses Google Authenticator. I did find that the problem came back, but I was able to flush the JS cache again and be able to get to the relationships. So flushing the cache was not a permanent fix. Sorry, should have come back and updated the thread.