teefers
(Doug Bennett)
1 July 2020 20:00
22
A separate option for adding to sitemap. Right now if you “remove” a page from navigation, it removes it from the sitemap.
Quite often you don’t want a page in the general navigation (links in a footer as an example) but still want it in the sitemap.
10 Likes
ttang
(Tommy)
2 July 2020 07:45
23
Provide a “print” function to print a Project’s information for documentation: e.g. site map, list of pages and sub-pages, list of stacks, partials and theme used in a page etc.
14 Likes
Elixir
(Adam Shiver)
3 July 2020 01:27
24
How about optional SMTP support for the contact form page style?
8 Likes
Anonymous
(Anonymous Coward)
3 July 2020 13:07
26
This is a great idea! To Adam’s credit, he probably referring to this thread. Without SMTP, receiving mail servers are treating the RW contact form as spam. Two people have hit it this week.
Hi, I am using the latest Rapid Weaver and have an existing site built through it that I have just amended slightly.
The contact form has stopped working even though I have not amended this page. I have added another contact page type form for T&C acceptance and that doesn’t work either. I have done a different email address on the new form too.
Previously, for some reason, any contact came into my junk filter, but not a problem as I have a seperate email client checking that. Now I am getting…
1 Like
The costs I totally agree with.
Make it more stable; RW8 crashes consistantly if cmdZ is used, well for me today, just flitting through Firefox and RW8 in preview mode has caused it to crash half a dozen times.
3 Likes
douga
(doug a)
4 July 2020 21:38
29
This has been mentioned before, but the biggest one for me is compatibility with older versions of MacOS, at least back to 10.13. So far, that’s the case, but as Apple continues to complicate things, this may become an issue everywhere.
2 Likes
With every new version of RW I dream of less emphasis on new features and more on squashing bugs and improving performance. Will that ever happen?
16 Likes
dan
(Dan C.)
5 July 2020 19:35
31
That’s one of our goals for RW9. Expect small on the surface changes, with a focus on bug fixes, speed enhancements, and compatibility with macOS 11.
10 Likes
dan
(Dan C.)
5 July 2020 20:40
33
A little more information is available here:
Hello Weavers,
Not sure if any of you watched the keynote yesterday but it was jam packed with exciting software announcements and the future of Mac hardware. All in all, it was a pretty great event. If you missed the event, you can check out the news here: Apple Events - Apple
I just wanted to let you all know where we are with RapidWeaver and the future of the Mac. In short, things are looking pretty good!
Here’s some more details on our current roadmap and plan, but please remember: nothin…
We’ll elaborate as we get closer to launch (or perhaps a semi-public beta for forum members).
Cheers
Dan
2 Likes
Flash
(...)
5 July 2020 21:16
34
Sounds like this is basically going to be another maintenance release. I was really hoping for some real innovation this time around. Like Big Sur is doing. Tons underneath but plenty of new and creative functionality.
Sorry if this sounds like a Negative Nancy comment.
2 Likes
dan
(Dan C.)
5 July 2020 22:40
35
Bigger things are coming, but the first big thing will be RW9 + Big Sur + Apple Silicon Support!
4 Likes
Flash
(...)
6 July 2020 00:25
36
Just concerned as we have heard this before.
Is there any point then to RW’s own blog feature, if even RW don’t use it? It’s not as if they haven’t had the option to develop the RW Blog function.
I do find it says a lot about RW when they don’t use their own blogging feature in their own app when creating their own blog! If it’s not good enough they should have rectified it long ago, after all, they are the developers. It highlights a dead built in feature. Considering the majority of sites need or use a blog, it surprises me that RW does…
frOM
(Olivier Mergault)
6 July 2020 10:21
38
“* Could you add the ability to the link dialog to add an anchor point to an internal page?”
Is it so difficult to implement ? I wonder why it still has not been done yet.
1 Like
instacks
(Jannis from inStacks Software)
6 July 2020 11:19
39
Because the link selector doesn’t know about any anchor points (= content) on the page.
ablx
(ABLX)
6 July 2020 17:38
40
Auto Save… Auto Save… Auto Save…
Oh and incase I didn’t mention it
AUTO SAVE!!
6 Likes
Auto Save?
Only if it’s safely implemented.
I’d almost rather not have the auto save unless the stability is addressed first.
2 Likes