I inserted CSS site wide code into my project quite a while ago. 6.3.5 broke that, I am back to 6.3.4. Thanks a lot!!! This version may fixes some bugs, but invented at least one new one.
I’m not using css, but I updated and now the “Foundations”, stack is missing, along with other add ons. I received an error message saying the page couldn’t published, because foundations stack is missing.
Afterwards, a dialogue box popped up stating, continue using as trial or register. I placed my registration code in the box, RapidWeaver opened as if it was my first time making this purchase.
Restart your Mac. OS X is not allowing us to locate your addons.
What “broke” exactly? Is the code not being inserted into your site?
I applied CSS to alter the padding of some extra content areas. That worked fine until I updated to 6.3.5. With 6.3.5 the theme presets for the padding overruled my site wide code. I went back to 6.3.4 and everything was as expected.
Could we get a copy of your project file to take a look at? Email to email@example.com.
OK! Done! You have got mail!
Did you ever receive a resolution to this? I’m experiencing the exact same problem. Please update if you have one! Thanks!
Please drop us a note - firstname.lastname@example.org - with a copy of your .rw6 project file and we’ll take a look at what’s going on!
Not at all, no solution in sight! Still waiting.
Could you confirm the issue is still present in 6.3.6 beta?
I took a gamble and published my site even though the CSS wasn’t rendering in preview mode in Rapidweaver. Lo and behold it published just fine with all CSS in place, even new code I just added. There seems to be an issue with the rendering of CSS in Preview mode. No clue what is causing it but at least it isn’t affecting what gets published to the web.
Drop us a note: email@example.com with the .rw6 project file. Do you have CSS consolidation enabled?
Test with beta 6.3.6
Still weird glitches. Preview in RW 6.3.6 looks fine. Previews in Safari and Firefox still show the same glitch. See attached screenshots.
Problem is solved with the latest beta based on 6.3.6. Glad that we found the problem. Thanks to the team, great job!