Version 1.1 soon?

Still battling the lack of refresh/update where when a theme page is created...

deleted dat file, latest versions of OS and DW etc etc

very frustrating. Pages still show original template data which should have been stripped out when the page establishes ties to the theme...

Yes, you need to go to Modify->Templates->Update current page before it will refresh, or open up the theme and save it and click "update all".

We will address this in a dot release in the next couple of weeks, but it should be very easy to work around in the meantime.

In fact the page should function properly without ever updating... it is just a cosmetic issue.

Originally Said By: Ray Borduin

  Yes, you need to go to Modify->Templates->Update current page before it will refresh, or open up the theme and save it and click "update all".


In fact the page should function properly without ever updating... it is just a cosmetic issue.  

Happy happy , joy joy...

Works as you said. I like my cosmetics to be clean so the duplicate template code stood out.

Thank you for the update.

With further progress and usage it will be interesting to see if you can render the page that has the theme and framework applied rather than just the literal contents.

As it is now there is the bug where there is no updating and clearing of the templates layout unless you update the template. BUT, this seems to be a trade off. We need the code to be updated but still see the page rendered as it is now when not refreshed.

Yes, we will try to address this problem in a future version. It isn't really possible to do directly, but we have a few tricks and ideas we can try to get around the problem.... most likely we would have you open up the theme design page, and then give you a floating interface to load pages into it and allow you to edit them in context this way... however that is easier said than done and may not even be possible.

If that doesn't work we will experiment with other ways that it could be possible, but because of the difficulty it won't likely show up until a full version update and not a bug fix dot release which could fix the auto update issue.

Originally Said By: Ray Borduin

  Yes, we will try to address this problem in a future version. It isn't really possible to do directly, but we have a few tricks and ideas we can try to get around the problem.... most likely we would have you open up the theme design page, and then give you a floating interface to load pages into it and allow you to edit them in context this way... however that is easier said than done and may not even be possible.

If that doesn't work we will experiment with other ways that it could be possible, but because of the difficulty it won't likely show up until a full version update and not a bug fix dot release which could fix the auto update issue.  

Maybe load the template values into the page until "save". Then remove on save to set the proper streamlined values. OR give us the means to set template code back into the themed page until we manually Update Current Page.

I know that working with this as a bug finds real appreciation of the bug while designing. Then Update Template, we can only deal with the literal content which changes your perspective as a designer. If we have to switch between an actual browser view and the code view, it sets a speed bump in place.

Maybe you should not even fix this bug if there is not a reasonable alternative.

Workflow is important to designers and not fighting apps is key.

Additionally the CCS Menu extension is a nightmare based on it rarely updating the changes made by the user. Usually it takes 3 or more attempts before it properly updates and is written to file. Very frustrating. While I'm on roll the Security Extension is additionally a exercise in frustration getting additional validation fields to load (User and Password for instance). Try once, fail, try again, accept only one value, save, try again, restart DW.... Arrr :) NOTE: I run all the latest version Extensions, DW and OS (Mac) finding the same problem on my new Laptop and 2 year old workstation.