RapidWeaver 8.2 Public Beta 1 (20697b) — UPDATED BUILD


(Dan) #1

Updated April 23rd

Hey Weavers,

New build is now available that fixes the “RapidWeaver is not previewing correctly” bug. Grab it here:
Download RapidWeaver 8.2 ( 20698b). This is essentially beta 2.

Please let us know if you find any more issues.


Original Post

Hello Weavers,

Just in-time for the weekend we have a brand-new build of everyone’s favourite website builder. As usual, all the details are below.

Please remember this is BETA software and as such may contain bugs! If you rely on RapidWeaver for mission-critical work do not use the beta builds, stick to the official releases.

What’s New in RapidWeaver 8.2 Public Beta 1 (20697b)?

  • Fixed a bug where RapidWeaver would appear to hang during publishing (possibly caused by OpenSSL and certificate/server issues)
  • Fixed up a tonne of issues with the Photo Album page type
  • Contact form now updates correctly when changing page properties
  • Control + Left Click a resource in the resource browser now works correctly
  • Improved performance when accessing files, especially from remote drives
  • Fixed a crash in the crash reporter, and it does make you wonder if perhaps we need a crash reporter for the crash reporter.
  • Fixed an issue where preview would get stuck in an endless loop (or dare I say infinite loop).
  • Fixed an issue when saving with an image attachment in styled text areas would deadlock the app

I’m happy with the risks of using beta software and would like to Download RapidWeaver 8.2 Public Beta 1 (Build 20697b).

If you find any issues please report back on this thread with details on how to re-create the bug and we’ll get it fixed for the next beta.

Have a great weekend!

Cheers
Dan


Can’t upload anymore!
Problem with Sitemap plus, cannot export, is there an alternative?
(Mathew Mitchell) #2

Preview feature does not seem to work correctly. When I use Command-P what I see within Safari is always the N-1 version of the page. So if I make a change then I only see the previous work. And if I’m previewing for the first time after going to a page with RW then I get some sort of error message. I’ve gone back to 8.1.7. But this behavior is very consistent.


(Dan) #3

@Mathew Not managed to re-create it here, can you send us you project?


(Mathew Mitchell) #4

Yes, glad to send it over. What email (or other) should I use?


(Dan) #5

@Mathew Thanks for that, we just pushed a new beta out that should fix the issue.

Update in-app or download it here: https://dl.devmate.com/com.realmacsoftware.rapidweaver8/20698b/1556033869/RapidWeaver8-20698b.zip


(Mathew Mitchell) #6

Yes, the issue is fixed! Many thanks.

If I notice any other issues I’ll let you know, but not noticing any big things right now.


(Gianluigi) #7

With last 8.2 beta, every time I enter in Sitemap Plus, RW freeze.
Back to 8.17


(Doug Bennett) #8

@tappo could you be more specific about what happens and when exactly it happens? Is it as soon as you add sitemap plus? Is it when you publish? Do you get any error messages? At what point does it freeze up? What version of sitemap plus are you running?


(robertreinink) #9

Also back to version 8.17 (20674) after experiencing this in version 8.2 (20698b)
looks like is doesn’t love Site Map plus 3.1.0 when trying to ‘export site’
RW crashes when adding Site Map Plus and trying to alter SMP settings.

NSInvalidArgumentException
-[RWSiteLayout pathToPage:fromPage:inDocument:relative:]: unrecognized selector sent to instance 0x6000003c25f0 We suspect this is caused by a plugin, please notify the developer of this problem.

SiteMap Plus (3.1.0) from YourHead Software

0 CoreFoundation 0x00007fff2bff8e45 __exceptionPreprocess + 256
1 libobjc.A.dylib 0x00007fff56c2b3c6 objc_exception_throw + 48
2 CoreFoundation 0x00007fff2c07354b -[NSObject(NSObject) __retain_OA] + 0
3 CoreFoundation 0x00007fff2bf9ae98 forwarding + 1478
4 CoreFoundation 0x00007fff2bf9a848 _CF_forwarding_prep_0 + 120
5 SiteMap 0x000000010ca8e88e SiteMap + 55438
6 SiteMap 0x000000010ca905bc SiteMap + 62908
7 SiteMap 0x000000010ca903fc SiteMap + 62460
8 SiteMap 0x000000010ca856ee SiteMap + 18158
9 RWKit 0x00000001021b5dd9 -[RWExporter pageContents:params:] + 622
10 RWKit 0x00000001021a10f8 -[RWExporter _exportPage:subPagePath:toPath:inRoot:usingName:] + 5648
11 RWKit 0x00000001021b3886 -[RWExporter _exportPage:subPagePath:toPath:inRoot:usingName:includingChildren:] + 279
12 RWKit 0x00000001021b49c7 __45-[RWExporter _exportPages:toPath:completion:]_block_invoke + 90
13 Foundation 0x00007fff2e1f06dc NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK + 7
14 Foundation 0x00007fff2e1f05e4 -[NSBlockOperation main] + 68
15 Foundation 0x00007fff2e1c635d -[__NSOperationInternal _start:] + 685
16 Foundation 0x00007fff2e1f0317 __NSOQSchedule_f + 227
17 libdispatch.dylib 0x00007fff584025f8 _dispatch_call_block_and_release + 12
18 libdispatch.dylib 0x00007fff5840363d _dispatch_client_callout + 8
19 libdispatch.dylib 0x00007fff58405de6 _dispatch_continuation_pop + 414
20 libdispatch.dylib 0x00007fff584054a3 _dispatch_async_redirect_invoke + 703
21 libdispatch.dylib 0x00007fff584113bc _dispatch_root_queue_drain + 324
22 libdispatch.dylib 0x00007fff58411b46 _dispatch_worker_thread2 + 90
23 libsystem_pthread.dylib 0x00007fff5863d6b3 _pthread_wqthread + 583
24 libsystem_pthread.dylib 0x00007fff5863d3fd start_wqthread + 13


(scott williams) #10

I would let @isaiah know he is the Caretaker of the SiteMap plug-in


(Isaiah Carew) #11

looks like it’s time for a sitemap update.


(Isaiah Carew) #12

What’s been happening

SiteMap and PlusKit use the RWSiteLayout class. When some method signatures to this class change, it breaks these plugins.

@tpbradley seems to be cleaning up of these methods. That’s great and I’m sure RW is getting better because of this work. This class is marked private, so no depreciation warnings are given obviously.

How we got here

In a perfect world no plugin would use a method marked private. However, I suspect that when these plugins were first written the public/private designations had not yet been put in place. If I recall correctly, that was by Andre around 2008, although I could have this wrong, I’m not certain. At the time Andre tried to work with us to make the necessary classes public – for whatever reason this class never was. It’s still private despite housing some very useful API bits.

However these plugins got here – they are here now – have many happy users – and I’m their new guardian. I imagine all those users would appreciate a bit less crashing. RapidWeaver would be better overall if we could find a way to make that happen – hopefully without hindering RW improvements.

So, I figured it should be up to me to come, hat in hand, to request an API change. Here goes…

A possible solution:

Can I propose that a few methods in this class get exposed to a public API? Unsurprisingly both plugins rely on the pathToPage: methods. If these methods, or a similarly functioning protocol, could be made public I think it would avoid a lot of these crashes and needless update churning we’ve had recently in these plugins.

I’m in no way married to this proposal. I’ve provided it just to be constructive. I’d be happy with any solution that improves the stability and longevity of these plugins and the RW platform in general.

I think even Stacks could make use of these in certain cases where a stack (especially php things) want to have some info about the site as a whole. I don’t currently do this since Stacks is much more strict about the public/private methods – but it would be nice if I could someday.

An interrum request:

Until some permanent solution comes to pass, can I ask that you be a bit wary of these methods in RWSiteLayout. And please know that I’d change to some other solution if I could, but I can’t – there is no other way to get this info – so every change you make to these has the effect of causing crashes to anyone that uses that build – until I can adapt. I don’t want to slow down your improvements – but I also don’t want to see any unnecessary disruption of many users. I figured if you were at least aware of the disruption that it creates there might be a happy medium. :smiley:

// @dan

New versions

There are new versions of both plugins available as of a few minutes ago.

PlusKit v4.1.5 beta 1
Release Notes: http://yourhead.com/appcast/RW6/beta/PlusKit/release_notes_4.1.5b1_1346
Download: http://yourhead.com/appcast/RW6/beta/PlusKit/PlusKit_4.1.5b1_1346.zip

SiteMap v3.1.1 beta 1
Release Notes: http://yourhead.com/appcast/RW6/beta/SiteMap/release_notes_3.1.1b1_1171
Download: http://yourhead.com/appcast/RW6/beta/SiteMap/SiteMap_3.1.1b1_1171.zip


What's up with Preview mode?
Problem with Sitemap plus, cannot export, is there an alternative?
(P J Cousin) #13

Hello Isaiah, I downloaded and installed your update, it is working perfectly
Thanks.
This stack is very useful, I assume that many people use it, it would be a shame if it was not updated
Thanks again

PJ


(Isaiah Carew) #14

@heretix - i always try to keep it up date. recently it has been a bit more difficult with RW v8.1 and RW v8.2 both introducing some incompatibilities.

on the bright side, these little problems are very easy to fix and we’ve been fortunate that RW has released these in betas so we’ve been able to fix them long before most users see them in the final build of RapidWeaver.


(robertreinink) #15

Can confirm that the new PusKit and Sitemap beta’s are working in the latest 8.2 RW beta
Thank you @isaiah


(Dan) #16

(Dan) #17

FYI: New RapidWeaver 8.2 build is now available: