Wordpress URLs - post name only
Permalink Browser Info Environment
I have purchased this add-in and intend to use it to incorporate an existing Wordpress blog in concrete5. The current wordpress blog has good standing from an SEO perspective with the Permalink format blog.com/sample-post (ie /%postname%/ in wordpress). The blog also uses <!--more--> to show where to break up a post which render as "read more" links.
I would like to carry on uing the same permalink format in wordpress and concrete5 but only the two date/sample-post formats are available.
Is there a patch to allow me to use this permalink format (I have experimented with curl.php etc in /base and can get the URL links in the correct formatin concrete5 but when a link is followed I get a 404?
I would like to carry on uing the same permalink format in wordpress and concrete5 but only the two date/sample-post formats are available.
Is there a patch to allow me to use this permalink format (I have experimented with curl.php etc in /base and can get the URL links in the correct formatin concrete5 but when a link is followed I get a 404?
| Type: | Discussion |
|---|---|
| Status: | New |
I have exactly the same issue and would be grateful if you could advise how we get around this. Many thanks.
Is this a common permalink format?
If you add a new permalink format, you will need to add it in two places, well three. The first is in the "base" files for the add-on, such as the base for cURL and the base for AJAX. The default base is AJAX, so it works on the client-side and goes easy on your server. However, when a search engine is detected, it switches to cURL to make sure they get all your content.
Secondly, there is a "model" packaged with the add-on which helps make the virtual URLs function as they should. This decides when to intercept URLs and make it redirect back to the add-on.
If you add a new permalink format, you will need to add it in two places, well three. The first is in the "base" files for the add-on, such as the base for cURL and the base for AJAX. The default base is AJAX, so it works on the client-side and goes easy on your server. However, when a search engine is detected, it switches to cURL to make sure they get all your content.
Secondly, there is a "model" packaged with the add-on which helps make the virtual URLs function as they should. This decides when to intercept URLs and make it redirect back to the add-on.
Thanks for the reply, I had already worked out a patch for the "base" files. The model file amendment will take a bit more thought.
It is a common permalink format (shown as fifth choice in suggestions - post name) see attachment. I think it would be worth including as standard.
It is a common permalink format (shown as fifth choice in suggestions - post name) see attachment. I think it would be worth including as standard.
Okay, great.
It seems this wasn't an option when I first created the add-on... I suppose WordPress added it in a newer version, and I hadn't noticed?
Try downloading WordPress for Concrete5 1.6.2, which I just published, which should have support for the "Post name" permalink style :)
It seems this wasn't an option when I first created the add-on... I suppose WordPress added it in a newer version, and I hadn't noticed?
Try downloading WordPress for Concrete5 1.6.2, which I just published, which should have support for the "Post name" permalink style :)
Fantastic, I installed 1.6.2 and it does exactly what I need.
Maximum karma points :-)
Maximum karma points :-)