The bug I was experiencing was the “export bug” wherein pages where exported but the process was “weird” (i.e. exported, then published) and left all the pages marked as changed. Hopefully this will be fixed for 7.0.4 or 7.1. But I’m hopeful that now some key bugs are sorted, that some others can get solved!
@apfelpuree A protocol-less or protocol-relative url’s are a url’s that begin :
As opposed to:
//www.example.com/style.css, that is a protocol-relative URL; it uses the same protocol as what the browser is already using to request the referring page. For example, if the browser had requested a page with https://www.example.com, then that URL will be requested over HTTPS and not HTTP.
Just tried to use the new Alpha Colour option in a theme but it didn’t work. Do we also have to make changes to the theme color section for the individual colors (they had to be in hex before). Tried it with rgba() but this will make RW hang.
The firewall alert is indeed related to RapidWeaver’s use of a PHP web server. The latest version 7.0.3 beta 3 should fix an issue where some people were seeing an empty preview page, but the fix also caused this firewall alert issue. This should be fixed in the next beta
There was an php-option in the firewall settings set to “do not allow”. To change the settings in the osx firewall you must be an admin and RapidWeaver has no admin rights. Its not possible that RapidWeaver can change the settings without permission by the user