LOVE the way the RMS guys are really listening to their customers. As I mentioned in a different thread, Dan and Aaron were very interested in my feedback during the beta period, and kept me abreast of issues I reported. And, it showed when they released v7 - after suffering through the previous release, this one has been pure joy.
Thank you @simon for chiming in and letting us know that you’re thinking about the best way to resolve the issue.
Cheers, Dave
I’d like to echo @dave’s comment. Version 7 has overall been a big step forwards. I realize there are some bugs (one that I’m experiencing lately) but they are all things I know you will sort out in short order.
However, the Sitelok and similar PHP issue is a big problem and I’ll probably continue to use RW6 for all my websites except one until it is sorted out: that’s how important this issue is in my workflow. (Put differently the very real strengths of version 7 are out shadowed by this one feature change.)
I don’t think I have any good ideas for a solution: I’d simply like to preview the relevant page. I certainly don’t need to see the PHP code “in action”. In the case of SiteLok I know what it’s going to do when published. So, I suppose if RW simply “ignored” the PHP and previewed the rest of the content that would work for me. (I don’t know, however, if that’s an adequate result for other folks.)
Yes I’d be happy if RW just ignored my PHP code the way it did in RW6.
I am working on a new PHP Project so I am going to follow this closely. wondering if I should create a
A plugin that can hold all the required libraries to my stacks and tell users its required once
B a Stack that would be a base but it would only be required once per project
Any thoughts would it work with the changes that have been made in RW7
Or am I barking mad making mountains out of mole hills
Another vote for RW to ignore PHP code in Preview.
You made my day (which was not too bad, anyway, sitting in a bar at a beach in Sardegna).
This is what brought me to RW and keeps me here.
Thanks for listening and interacting and, most imprtantly, taking action!
Hello Fellow SiteLok Users… And the RapidWeaver Team. I am just getting back into Rapid Weaver today as I am beginning an extensive upgrade to one of my companies sites. I am currently running RapidWeaver 6 and was planning to upgrade to RapidWeaver 7 tomorrow as it sounds like a really great step forward.
I want to be sensitive here as I am sure the RapidWeaver Team has put a huge amount of work into all this. Having said that I am a SiteLok user as well and what I love about the SiteLok approach is how I can pepper the php snippets throughout my site and the pages themselves to accomplish some truly custom solutions. A little concerned what I am going to be up against with an upgrade to RW 7. It is simply not an option to add all this once the site is built. For me the implementation of the many SiteLok snippets is an part of the overall build process not something simple that can just be popped in at the end.
Again I want to extend my gratitude and thanks to the RW Team for their efforts to make this new version the best ever and provide us with useful and helpful features. Just hope we can find a thoughtful way to move forward with this issue as SiteLok is an important tool for some of us.
Kind Regards,
Dave
Does anyone know if the RW 7.0.4 update fixed the SiteLok/Preview issue? Sounds like it is on the devs “ToDo list”.
Sadly, no… a real showstopper for me.
Ah, too bad! I am really going to need this for a project in the fall, so I hope it’s at the TOP of the “fix” list.
I have approximately 20+ pages in one website that uses Sitelok. My workflow since RW7 was released is this: When editing an individual page I cut (command+X) the Sitelok prefix, storing it on the clipboard while I edit and preview the page, then put it back in before publishing. There are other anomalies that make this process more difficult. Even tho, the Sitelok prefix no longer calls the Sitelok php scripts, the now orphaned blab plugin javascript causes all my submenus to drop down and obscure my view. Still, it is a cumbersome but effective workaround. I look forward to this getting fixed.
My workflow is similar - with the extra step of cutting my Sweet Button that logs people out.
I’m really hoping @dan and company can figure out a fix - some of my websites also have 20+ pages of Sitelok…not a fun task editing them.
Hey guys, good news, we’ve fixed the sitelok issue in RapidWeaver 7.1 
RapidWeaver 7.1 is currently being tested by third party developers (it has some big changes in it).
We hope to release a public beta in the next few weeks once we’re sure t’s stable enough.
Sorry for the delay!
P.S. Here’s the release notes we gave the developers (more changes/fixes are still being added). Enjoy this little sneaky look at what’s coming soon…
- Added back in support for re-publishing all files for a single page
- SiteLok plugin no longers breaks Preview mode
- Colour arithmetic in themes now works again
- Fixed an issue where the Filename extension was ignored when exporting (again)
- Fixed an issue where an updated resource would not get re-published
- Resizing Gifs now works (animation is not supported in resized gifs, yet)
- Cleaned up plugin loading code, it’s good to be clean!
- Fixed an issue under Sierra when using the Web Inspector
- Fixed a data loss issue
- Updated Voyager theme (Thanks Adam!)
A lot of things internally have changed in the way we load and save plugins, please test your plugins thoroughly and be on the look out for dataloss. We now lazy load plugins, this makes opening RW projects super, super quick. In our tests ALL sites now open in under a few seconds no matter the size!
- We added a new area in the sidebar for plugin settings
- Fix the typo in +clearSharedPluinDataForDocument:
- Removed RWPathUtilities from RMKit (FYI: just incase you were using it)
- Improved the global plugin data storage
Fantastic! Thanks to all your team for sorting this:grin:
@dan Yes, this is fantastic news. The Sitelok issue is very annoying so this is welcome news.
My second biggest gripe with RW7 (and RW6 actually) is that drag-and-drop approaches to using images don’t work with SVGs. I think you or someone at RM mentioned that you hoped to include SVGs as a drag/drop image option. Any closer to that?
With Adam’s beautiful Foundry option he only uses drag/drop. There are plenty of cases where SVGs would be the best choice but I’m currently forced to use non-Foundry stacks in those cases. There are a few other stacks I’d love to use drag/drop with also with SVGs.
Fantastic news @dan - many, many thanks for keeping this issue on your list of improvements. I realize that percentage of Rw users who incorporate Sitelok into their sites is probably pretty small- but as @Mathew said, it’s a huge annoyance.
I also agree that adding drag and drop for SVGs would be fantastic - especially in the LOGO area of site setup. (And, what?! No warehousing in Foundry?! Yikes!)
can’t wait to get my hands on 7.1 need to start a siteloke site fairly soon once my client gets his act together
Anyone tested the 7.1 beta with Sitelok? Any issues?
Excellent! Thanks for making sitelok a priority!
Thank you for this update @dan… Have had to put an important project off due to the SiteLok issue. Hope the fix not only resolves the issue but retains the fantastic preview features you have built into RW7.
Also want to express the desire for SVG support in RW7.
Kind Regards,
Dave