Both very good and necessary feature requests, we hope to see this in a forthcoming RW8 update.
2 Likes
Intuitive structure planning, ideally also for printing for the client like Adobe Muse
4 Likes
Isaiah: Thanks for your response. Hopefully these are things that can get worked out between RM and yourself in the near-ish future.
Cache busting links (css especially) generated when single page publishing used. Cache busting links are generated when entire site is exported or published but not updated/changed if single pages are published… At least, that is my experience. I’ve checked the css link code in the output. RWcache example:
<link rel='stylesheet' type='text/css' media='all' href='index_files/stacks_page_page16.css?rwcache=531945740' />
2 Likes
I reported this as a bug both with support and here back in January:
These are all things out of the hands or Realmac, you would need to contact Yourhead and request these.
2 Likes
Great suggestion, it would be a very useful feature, yes indeed.
1 Like
These are all things out of the hands or Realmac, you would need to contact Yourhead and request these.
i’ve seen them. all good ideas. i’ll see what i can do. 
3 Likes
Thanks a lot for the information.
That’s not a bug, or at least not something we can fix. It’s a side-effect of using Cloudflare.
1 Like
@dan
Sorry wrong post referral above.
No CloudFlare involved with this issue. It can be recreated publishing to a local drive.
The cache busting link doesn’t get updated every time unless republish all files.
1 Like
I concur… It can be verified by simply looking at the output page code. the cache timestamp doesn’t change unless entire site is exported or published. Single page publishing (with or without child pages) does not update the “cache busting” timestamp. I don’t use CloudFare and it’s absolutely an issue for me.
3 Likes
I know this is a logistical challenge, but I would really like cleaner code output. Right now if you look at the source code of a RW + Stacks built site there is a lot happening.
2 Likes
I know this is a logistical challenge, but I would really like cleaner code output. Right now if you look at the source code of a RW + Stacks built site there is a lot happening.
Currently Stacks pages are built up from many components from many different developers – all with their own styles and interpretation of the best tradeoffs between readability and concision.
I don’t think we’ll get all the stack developers to come to any sort of agreement on code style or the correct split in that tradeoff. So what I think is probably best is to introduce automated code cleanup.
In Stacks 3.5 I built in the Tidy library. A very mature open source library for doing exactly this.
Currently this is only developer feature. Tidy provides the errors and warnings in the dev console. But it doesn’t currently modify anything, it’s purely informational.
I don’t want to make any promises yet, but I think it’s safe to say Tidy will play a bigger role in not just reporting errors – but also cleaning up and compacting code. The details here have yet to be completed – so if you have any specific technical requests – add them to the Stacks public bug/feature tracker. That way I can’t ignore them when it comes to development time. It’s the best way to keep me honest.
Isaiah
4 Likes
This topic was automatically closed 6 days after the last reply. New replies are no longer allowed.