In the last two weeks I lost the top left expand arrow and top right settings gear on all my cards. First thing I thought to do was remove the content from the *css card to see if that was suddenly causing a problem - maybe because of the update to 1.12.0. I'm hosted on CldStr and I guess they auto-updated.
I took out the content, refreshed the page and nothing changed. The CSS remained the same. Weird. Hard refresh and still no change. Then I went to the tinyMCE card and took all it's content out thinking that maybe it's contents contents contained something screwing up my headers. I think that's what did it.
Now, whenever I go to edit any card in my wagn, I get a "404: Bad Address". I've tried with different accounts in different browsers. Scary. Please help!
url?
We have no information about your cloudstore account; you can email info@cldstr.com for support that knows about your account. we just know about wagn :)
Wow you're fast. :)
My wagn's URL is http://disasterrelief.flosolutions.org/wagn
My account name is devinbalkind@gmail.com... and I'll send that info on over the cldstr folks.
I'm heading off to sleep soon, but here are some workarounds:
1. you can get the edit form by adding ?view=edit to your urls
2. I think you'll be able to fix the edit problem (and many others) if you get a valid *tinyMCE setting. That's broken, and it appears to be breaking javascript (including the menu). You can copy the value from wagn.org to your "*tiny mce" card: http://wagn.org/*tiny_mce.txt
3. the missing icons are just one bad image reference in the css. I looked at the raw css, and it looks fine to me, so I think that will get fixed if you re-save the card named "*all+*style" (which will regenerated the cached css).
If you have trouble with any of these, I should be able to help tomorrow.
Yep. tinyMCE is back. 404 Errors are gone. Resubmitting the "*all+*style" got the little icons back. Thanks so much!
nice! Sorry you had to deal with any of that. I'll be posting patches soon, though I don't anticipate you'd have any further problems in the meantime unless you change your tinyMCE (a coming patch will insure wagn handles tinyMCE configuration errors more robustly!)
As of Wagn 1.12.1, default tinyMCE configuration is JSON, not javascript. This is more secure (though there wasn't ridiculous vulnerability before unless you gave too many people permission to edit the *tinyMCE card), and it means that faulty configuration won't break anything (though, of course, tinyMCE might not look the way you want it to).
Also the stylesheet handling has been reworked to avoid CSS problems like yours. In fact, the relative path handling has been overhauled to make things more robust for non-root wagns. Very happy about that! :)