Publishing issue RW Classic 9.4.3

Classic
1

I’m facing a publishing issue for the first time as far as I can remember.
After being off for 5 weeks, I had some updates for CMS, Foundation and RW. After this, I had one page (blog) to refresh and publish. Unfortunately, this publishing does not go to the end. Randomly, some of the files remain not uploaded, and the blog page is blank or just partially displayed (depending on which files have been uploaded).
I have also lost the list of my blog articles on the admin page. I’m not sure if the updates are the origine of this, but I did not anything else.

In the preview mode, I get this error:
Fatal error : Uncaught TypeError: array_slice(): Argument #1 ($array) must be of type array, null given in /private/var/folders/03/p796h58n23vfhl0kvb6ys8mh0000gn/T/com.realmacsoftware.rapidweaver8/RapidWeaverClassic/9560/document-0x7fad1fd08ae0/RWDocumentPagePreview/blog/index.php:2548 Stack trace: #0 /private/var/folders/03/p796h58n23vfhl0kvb6ys8mh0000gn/T/com.realmacsoftware.rapidweaver8/RapidWeaverClassic/9560/document-0x7fad1fd08ae0/RWDocumentPagePreview/blog/index.php(2548): array_slice(NULL, 0, 18) #1 /Applications/RapidWeaver.app/Contents/Resources/RWWebServerLaunch.php(175): include(‘/private/var/fo…’) #2 {main} thrown in /private/var/folders/03/p796h58n23vfhl0kvb6ys8mh0000gn/T/com.realmacsoftware.rapidweaver8/RapidWeaverClassic/9560/document-0x7fad1fd08ae0/RWDocumentPagePreview/blog/index.php on line 2548

My RW version is 9.4.3 and the php 8.4.5, Total CMS v1.13.32 (17377).

I would appreciate any suggestion for this point.

2

Hi @zdenek,

Sorry to hear you’re having issues. Hopefully, we’ll be able to get you back up and running as soon as possible.

The first thing I’d try is restarting RapidWeaver and then selecting “Re-Publish All Files” from the File menu to see if that resolves the issue.

I’ve also cc’d @joeworkman, as he’s the developer behind Total CMS and Foundation, to see if he’s encountered this issue before.

Fingers crossed the re-publish fixes it :crossed_fingers:

3

Hi Dan, thank you for your reply, here is an additional information: If I re-install RW version 9.4.0 (also without the CMS and Foundation updates), I’m facing the same issue: the publishing of any page if frozen before the end, so randomly, a part of the files is not published. I will also check with the host tomorrow and revert to you.
It looks like the “FTP door is not completely open” - and I do not understand why

An exemple below

Capture d’écran 2025-05-01 à 22.05.39
Capture d’écran 2025-05-01 à 22.05.391094×566 35.6 KB

Capture d’écran 2025-05-01 à 22.06.41

4

You might want to try lowering the number of connections. Switch it to 1 and see if that helps.

CleanShot 2025-05-01 at 10 .01.03@2x
CleanShot 2025-05-01 at 10 .01.03@2x1372×1220 139 KB

You could also export your entire site locally, then use another FTP client to upload it.

Let me know how you get on trying those!

5

This problem doesn’t seem to be with RW. According to my host, it’s their security rules that are blocking the FTPS transfer, considering it aggressive. No answer so far as to why this is suddenly happening. I’ve opened a ticket and will keep you posted later.

Additionally: The host proposes to post my site in local mode and then transfert the files via a soft like FileZilla (I don’t use it, but Cyberduck). I’m not sure this would be an option due to a part of my site (Blog) managed by TCMS. The CMS-data folder is not generated in the local post ?!?
@dan - might this be an option or not? My understanding is the during the post, there are some links generated directly between TCMS and the web structure of the site - am I correct?

1 Like
6

I’m still in discussions with the host company to find a solution to my persistent problem.
He asked me to do some tests by changing the output port. I know that this option was available in older versions of RWC, but not in the current one. Is there any way of setting it?
If not, where could I see which port is used ?

7

Hi @zdenek,

There’s no field for the port in the publishing settings, as FTPS uses a number of ports during the transfer process. It normally starts out at port 21 (explicit mode) or 990 (implicit mode) for handshaking, but then switches to another port for the actual data transfer. Which port(s) that is (are), is negotiated during the initial handshake at port 21 or 990 and can’t be predefined.

If your host uses something else than 21 or 990, then ask them to adhere to standards. There’ not called standards for nothing :slight_smile:

Does your host offer SFTP or plain-old FTP?

Cheers,
Erwin

8

If you’re using SFTP you can add a port number to the end of the server address like this…

image
image1344×1226 96.2 KB

9

Hi @dan,

Does that work for FTPS too though?

Cheers,
Erwin

10

Yes I believe so, although I haven’t tested that myself!

1 Like
11

I’m not yet completely fixed with host. Directly from RW it worked only with FTP. I think this is really related to the ports opened in my host server. FTPS starts and after transferring 1-2% of files freezes. SFTP freezes directly.

12

The host moved my website to another server - I got this message:

The new web server on which your site is now hosted uses a more recent version of the FTP server.
In order to confirm our assumption, we would need you to check, as far as possible:

The version of the TLS/SSL protocol used by RapidWeaver to establish the FTPS connection;

The cipher suites used;

And whether it is possible in the application to force a more recent version of the TLS protocol (ideally TLS 1.2 or 1.3).

Could you please provide the above informations?

13

@dan or @dang should be able to provide that information

Cheers,
Erwin

14

Hi @zdenek,

RapidWeaver Classic 9.4.3 uses Curl version 7.79.1, OpenSSL version 1.1.1m, and libssh2 version 1.10.0 which supports the following TLS versions.

  • TLS 1.3
  • TLS 1.2
  • TLS 1.1 and 1.0 (supported but deprecated)

I’m afraid I don’t have a full list of supported ciphers for this release. However, we’re releasing an update for RapidWeaver Classic later today that updates these three libraries to the latest versions :tada:

I’ve also added a method to list the supported ciphers to the support log file accessible from Help → Troubleshooting → Copy Support Logs. Note that you’ll also need “Enable upload logging” ticked in the Publishing tab within the app preferences.

Below is the output you’ll see in the log file showing the library versions along with all supported protocols and ciphers.

Please try publishing again with version 9.5.0 when it becomes available.

Hope this helps!

cURL Version: libcurl/8.13.0-DEV OpenSSL/3.5.0 zlib/1.2.12 libssh2/1.11.1
cURL Supported Protocols: file,ftp,ftps,http,https,mqtt,scp,sftp
cURL Supported Ciphers: TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_AES_128_GCM_SHA256,ECDHE-ECDSA-AES256-GCM-SHA384,ECDHE-RSA-AES256-GCM-SHA384,DHE-RSA-AES256-GCM-SHA384,ECDHE-ECDSA-CHACHA20-POLY1305,ECDHE-RSA-CHACHA20-POLY1305,DHE-RSA-CHACHA20-POLY1305,ECDHE-ECDSA-AES128-GCM-SHA256,ECDHE-RSA-AES128-GCM-SHA256,DHE-RSA-AES128-GCM-SHA256,ECDHE-ECDSA-AES256-SHA384,ECDHE-RSA-AES256-SHA384,DHE-RSA-AES256-SHA256,ECDHE-ECDSA-AES128-SHA256,ECDHE-RSA-AES128-SHA256,DHE-RSA-AES128-SHA256,ECDHE-ECDSA-AES256-SHA,ECDHE-RSA-AES256-SHA,DHE-RSA-AES256-SHA,ECDHE-ECDSA-AES128-SHA,ECDHE-RSA-AES128-SHA,DHE-RSA-AES128-SHA,RSA-PSK-AES256-GCM-SHA384,DHE-PSK-AES256-GCM-SHA384,RSA-PSK-CHACHA20-POLY1305,DHE-PSK-CHACHA20-POLY1305,ECDHE-PSK-CHACHA20-POLY1305,AES256-GCM-SHA384,PSK-AES256-GCM-SHA384,PSK-CHACHA20-POLY1305,RSA-PSK-AES128-GCM-SHA256,DHE-PSK-AES128-GCM-SHA256,AES128-GCM-SHA256,PSK-AES128-GCM-SHA256,AES256-SHA256,AES128-SHA256,ECDHE-PSK-AES256-CBC-SHA384,ECDHE-PSK-AES256-CBC-SHA,SRP-RSA-AES-256-CBC-SHA,SRP-AES-256-CBC-SHA,RSA-PSK-AES256-CBC-SHA384,DHE-PSK-AES256-CBC-SHA384,RSA-PSK-AES256-CBC-SHA,DHE-PSK-AES256-CBC-SHA,AES256-SHA,PSK-AES256-CBC-SHA384,PSK-AES256-CBC-SHA,ECDHE-PSK-AES128-CBC-SHA256,ECDHE-PSK-AES128-CBC-SHA,SRP-RSA-AES-128-CBC-SHA,SRP-AES-128-CBC-SHA,RSA-PSK-AES128-CBC-SHA256,DHE-PSK-AES128-CBC-SHA256,RSA-PSK-AES128-CBC-SHA,DHE-PSK-AES128-CBC-SHA,AES128-SHA,PSK-AES128-CBC-SHA256,PSK-AES128-CBC-SHA

1 Like
15

Hi @tpbradley,
Yes, this update has fixed my issue. Thank you to everyone who looked into my problem.

16

Excellent, that’s really great news!

Cheers!