Total CMS Trial and RapidWeaver Blogging Course

I have bought Ben´s Blogging Course, installed Total CMS TRIAL (Rapidweaver 6.4 , Foundations and Stacks 3.5) and I am at the 4th video (Displaying individual Posts).

I can´t have the Articles (ex-Home page) with Blog List linked to the Article Page (Blog Post). Connecting each Article from the Blog List to it´s individual display page.

When clicking on the Article Blog List title it stays at the same page, and on the server side it goes to a non existent URL. (http://blog.360portugal.com/var/folders/m4/dj0jjkyx3xnckrbl9k9p9vyw0000gn/T/com.realmacsoftware.rapidweaver6/RapidWeaver/1613/document-0x7f8b35fd2500/RWDocumentPagePreview-64/article/index.html?permalink=se-catedral-de-braga)
I have all CMS ID correct.

I don´t know what to do. I can´t find Ben Counsell contact.

It might be hard to help without a bit more info. And while ‘watch this video’ probably isn’t the answer you’re looking for, Joe put out a video within the past month which might help:

Thanks, I have followed this video, and started from zero, deleted all my files from the server using FileZila, and the error repeats : No connection between Blog List and Blog Post (display side) giving me a non existent URL error when clicking on one of the Blog name in Blog List.
My PHP version is * Server version: 5.6.32-78.1 - Percona Server (GPL), Release 78.1, Revision 8bb53b6

Sorry guys but the TRIAL TOTAL CMS does NOT WORK using Rapidweaver 6.4 Stacks 3.5 Foundations

Example: http://blog.360pportugal.com

I use total CMS with foundation and have done many sites in RW 6.4 with it. It absolutely DOES work.

It sounds like a server side configuration issue but not much to go on in your post.

Have you…
Previewed the blog POST page in RW?
Did you get a pop up window to write the path cinfig files to the server?
Did you click send?

Have you already tried pretty url settings? (If not ignor this part) If so, set it back to default and remove any .htaccess code you added for pretty url’s. Get it working in default mode first. Preview the blog POST page and resend the paths to the server.

Did you add the debug stack to a page to see if there are server issues?
Please post a screen shot.

I would also update your php to at lest 7.1

I’m quite sure with some more info we can get you going.

Do you have a ftp app? Worse case we can just edit your post url file and solve the path issue that way. It should look like this:
http://blog.360portugal.com/article/index.php?permalink=

1 Like

The problem is that Rapidweaver and TOTAL CMS TRIAL is creating wrong URL for each Blog Post, and it is obvious that the server is giving me ERROR404-PAGE NOT FOUND

This is the URL to the permalink “se-catedral-de-braga” :
([http://blog.360portugal.com/var/folders/m4/dj0jjkyx3xnckrbl9k9p9vyw0000gn/T/com.realmacsoftware.rapidweaver6/RapidWeaver/1613/document-0x7f8b35fd2500/RWDocumentPagePreview-64/article/index.html?permalink=se-catedral-de-braga ]
I have only 4 pages

This error happens even with pretty post URL

Have you contacted support?
support@weavers.space
That is the best place to go to get questions answered for something like this.

Also, get it working WITHOUT Pretty URLS first, that will be the first thing Joe will tell you to do.

Hi Santiago,
Yes I know what the issue is, the YourBlogName.posturl file in the /cms-data/blog/YourBlogName folder is either missing or contains the wrong path.

It’s a simple fix really, but as I said above, you need to turn pretty url’s off and remove any prettyurl related content you added to your .htaccess file first. It’s important to get it working with defaults before doing the more advanced stuff, especially if you are having issues.

You should also add the Debug Stack to your page and preview in RW to see if there are any server side configuration issues that may have caused this issue in the first place.

if all is well, you can just edit the .posturl file and you will be good to go.

I have turned this option ON as you mentioned, but the error is the same as in pretty OFF

The problem is happening also in preview mode with rapidweaver, when clicking in the Blog List it does not connect to the Blog Post.

The Admin pages are working correctly.

I understand this, but if you also added the .htaccess rules you need to remove them and set it back to default. If you tried it with pretty url’s on and did not make the .htaccess changes then that won’t work either.

I am just trying to get you back to the default setting with NO .htaccess rules for pretty url’s. Then we can move forward.

Yes, I am sure it is…
Did you actually add the debug stack to the page and preview?
Can you paste a screen shot of that (in preview mode).

The issue you are having is easy to fix, its a small edit to the .posturl file. But, if you don’t get back to defaults first or if you have a config issue on the server it will just take you round and round in a circle of not working.

Confirm that you are back to defaults, there are no .htaccess pretty url rules and show the debug stack screen shot and I will get you going.

1 Like

The Blog page with the Blog List Debug report is :
SERVER …
• __CF_USER_TEXT_ENCODING = 0x1F5:0x0:0x0
• SHELL = /bin/bash
• HOME = /Users/MacbookPro/Library/Containers/com.realmacsoftware.rapidweaver6/Data
• Apple_PubSub_Socket_Render = /private/tmp/com.apple.launchd.YPRnjjVhrv/Render
• SSH_AUTH_SOCK = /private/tmp/com.apple.launchd.posOpVab4V/Listeners
• PATH = /usr/bin:/bin:/usr/sbin:/sbin
• LOGNAME = MacbookPro
• XPC_SERVICE_NAME = com.realmacsoftware.rapidweaver6.202240
• USER = MacbookPro
• XPC_FLAGS = 0x0
• CFFIXED_USER_HOME = /Users/MacbookPro/Library/Containers/com.realmacsoftware.rapidweaver6/Data
• APP_SANDBOX_CONTAINER_ID = com.realmacsoftware.rapidweaver6
• TMPDIR = /var/folders/m4/dj0jjkyx3xnckrbl9k9p9vyw0000gn/T/com.realmacsoftware.rapidweaver6/
• PHP_SELF = -
• SCRIPT_NAME = -
• SCRIPT_FILENAME =
• PATH_TRANSLATED =
• DOCUMENT_ROOT =
• REQUEST_TIME_FLOAT = 1548800990.1088
• REQUEST_TIME = 1548800990 Notice: Array to string conversion in - on line 1081
• argv = Array
• argc = 1
ENV …
• __CF_USER_TEXT_ENCODING = 0x1F5:0x0:0x0
• SHELL = /bin/bash
• HOME = /Users/MacbookPro/Library/Containers/com.realmacsoftware.rapidweaver6/Data
• Apple_PubSub_Socket_Render = /private/tmp/com.apple.launchd.YPRnjjVhrv/Render
• SSH_AUTH_SOCK = /private/tmp/com.apple.launchd.posOpVab4V/Listeners
• PATH = /usr/bin:/bin:/usr/sbin:/sbin
• LOGNAME = MacbookPro
• XPC_SERVICE_NAME = com.realmacsoftware.rapidweaver6.202240
• USER = MacbookPro
• XPC_FLAGS = 0x0
• CFFIXED_USER_HOME = /Users/MacbookPro/Library/Containers/com.realmacsoftware.rapidweaver6/Data
• APP_SANDBOX_CONTAINER_ID = com.realmacsoftware.rapidweaver6
• TMPDIR = /var/folders/m4/dj0jjkyx3xnckrbl9k9p9vyw0000gn/T/com.realmacsoftware.rapidweaver6/
GLOBALS …
• Notice: Array to string conversion in - on line 1147
• _GET = Array Notice: Array to string conversion in - on line 1147
• _POST = Array Notice: Array to string conversion in - on line 1147
• _COOKIE = Array Notice: Array to string conversion in - on line 1147
• _FILES = Array Notice: Array to string conversion in - on line 1147
• argv = Array
• argc = 1 Notice: Array to string conversion in - on line 1147
• _SERVER = Array Notice: Array to string conversion in - on line 1147
• _REQUEST = Array Notice: Array to string conversion in - on line 1147
• _ENV = Array Notice: Array to string conversion in - on line 1147
• GLOBALS = Array
• publish =
• liEnd =
• liStr =

• pValue =

• pName = pValue

I have deleted my previous subdomain and started a new one just for this Blog test blog.360portugal.com
It is a fresh start, and the error is still there

Okay now we are getting somewhere.

I just put a test post in. http://blog.360portugal.com/blog/post.php?permalink=/test-for-permalink

Do you have a ftp app?
You need to edit the file /CMS-Data/blog/blog/blog.posturl

The post url should be:
http://blog.360portugal.com/blog/post.php?permalink=

1 Like

swilliam, I Thank you!! for your patience and persistence.

I did it, and it is working now!!

best regards

1 Like

Glad to hear, I’ve seen this behavior before I. RW6x, I’m not sure what causes it, but once you understand it’s simple to fix.

Keep in mind when you move your blog to a different url, you need to edit that file.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.