I’m working with Freeway 7, though I don’t think my problem here is necessarily version specific.
I started a project in which the Master page was auto-named as Master1, and predictably produced the master item css file…
<link rel="stylesheet" href="css/master1.css">
While still developing the project, I renamed the master page to “Master-Wide” to avoid having to remember the specific use of which numbered Master does what. What I expected was the master item css file name would also change…
<link rel="stylesheet" href="css/master-wide.css">
However, instead of renaming the master item css file, Freeway has left it as master1.css. I’ve tried deleting the Site Folder contents, force republishing, non-hyphenated names, etc. etc.-- does anyone know how to make Freeway catch up to my current css naming structure?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I have had perhaps a related problem, though it was easy to fix with extended code. I changed the color of a type style for footer type I use only on my Master Page and I couldn’t get Freeway to upload the change. In the style sheet the previous color remained specced. Worked fine within FW7 and locally, but not on upload.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I think I know what Ernie means, though having no answer at all. Recently having had a talk with Hanna these days, which points into the same direction:
http://freewaytalk.net/thread/view/158802#m_158802
But shame to me didn’t follow this consequently. So calling this a bug is a guesswork.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
http://freewaytalk.net/thread/view/158802#m_158802
Good call, Thomas-- so I’m not the only one concerned by this.
In my case, the master1.css file is doing exactly what it needs to… serve the css code for master items. It’s just the master page it represents is no longer called “master1”. So when I start using multiple masters, will I need a cheat-sheet to keep track of which master is which? This is my concern.
Since renaming the master is an option in Freeway, I would have thought the logic would extend all the way to the page code. It should, as the appearance of control is truly not a feature or benefit.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I’ve done a few experiments, and it seems that Freeway has no problem changing the master css filename early in the construction process. However, once a certain quantity of items have been added to the page (I don’t know how many) it is no longer able to change the name.
I resolved my immediate issue this way: I duplicated the master and named the new one as I wanted, applied it to the children, then deleted the old master. The children now have a master css link that I can match to an existing master page.
The downside is all the child content added before this step is over-written and lost. So, something the developers should look at in their spare time.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 7 Apr 2015, 4:02 pm, The Big Erns wrote:
I’ve done a few experiments, and it seems that Freeway has no problem changing the master css filename early in the construction process. However, once a certain quantity of items have been added to the page (I don’t know how many) it is no longer able to change the name.
A tick in my left big toe told me something similar, cause had indeed projects with no issues and projects having had this behavior.
I resolved my immediate issue this way: I duplicated the master and named the new one as I wanted, applied it to the children, then deleted the old master. The children now have a master css link that I can match to an existing master page.
The downside is all the child content added before this step is over-written and lost. So, something the developers should look at in their spare time.
So theoretically, you should duplicate the child page too, create a new page, apply the new master to it and copy and paste the stuff from the old child-page step-by-step back into the new child.
I even make Backup Masters of “milestones-child-pages” - just to prevent me from this.
But 100% agreed and herby addressed to Softpress as well:
Have an eye on this!! Something is quirky. And work-arounds can’t be an answer.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options