I have WP 2.9 installed on an IIS 7 server. Permalinks works with the URL Rewrite add-on for IIS, but I'm wondering if it's possible to use different permalink structures for pages and posts. For instance:
Pages would be: www.url.com/$pagetitle/
Blog posts would be: www.url.com/blog/$entrytitle/
Is this possible?
Standard wordpress permalinks have page titles without dates, and you can also get rid of the date in posts: Customize Your Dated WordPress Permalinks - Perishable Press.
And get rid of the category base, too: Wordpress Supplies » Wordpress Plugins » WP No Category Base
What you're describing is actually the default behavior if you use a custom permalink (at least on Apache... it might be different in IIS).
Related
I've gotten the 4.3.08 fishpig extension working with my 1.7 Magento site (yes, I know it's a very old magento version). The integrated blog looks great and has the magento theme when I access it via the Site Address URL. However, I can still access the non-integrated blog when I type the Wordpress URL into a browser. That url doesn't have the integrated theme - it's just the plain posts. I don't want google to index that wordpress url or for users to find that url. I want them to only see the Site Address URL. I have done a ton of searches but can't seem to find how to do this. Looking for help!
You haven't included your URL so I can't provide accurate feedback. That being said, if configured correctly, the WordPress URL should give a 404 error page. This won't be seen by anyone and won't be indexed by search engines.
If the WordPress URL is visible and everything is configured correctly, you may be using the default permalinks (eg. /blog/?p=123). Change the Permalink structure at Settings > Permalinks and the WordPress URL should generate a 404 page.
I have a single instance of Magento running. I am using wordpress blog in magento and want to use magento "Blog" parallely. When i use both blogs magento blog overrides wordpress blog section. Can anyone tell me how we can solve this problem.
You can see the link http://dev.dynatrac.org/ where i want to use this section.
Thanks
Instead of using URL http://dev.dynatrac.org/index.php/blog.html, you can use http://dev.dynatrac.org/blog/ and put the wordpress installation in the blog directory of your magento root.
Now using .htaccess or nginx conf (depending upon whether you use apache or nginx) you can redirect the URLs in the form of http://dev.dynatrac.org/blog/something_something.html to blog/ directory.
Unfortunately, the AW_Blog extension uses 'blog' as it's router frontName. This overrides the Magento WordPress Integration extension, making the 2 incompatible. In an ideal world, AheadWorks would modify their extension to use a different router frontName (eg. aw_blog) and then would display the blog using a dynamic route (in the same way that Magento WordPress Integration does), thus allowing both extensions to function at the same time.
My advice would be to remove AW_Blog and instead, make use of the Custom Post Types add-on and Root.
The Custom Post Types add-on allows you to create custom post types in WordPress and display them on your Magento integrated blog. As an example, lets say you display your standard blog posts at /blog/ but wanted to create a different type of posts (eg. News articles). You could setup a custom post type called 'news'. By default, this would display all of your news posts at /blog/news/. To improve this, you could install Root, which would remove the /blog/ from the URL, meaning your news articles would be available at /news/.
This method allows you to create what appears to be multiple different blogs but is actually a single WordPress blog that makes use of different custom post types. This method will allow you to have as many different post types as you require.
EG.
http://www.yourmagento.com/blog/
http://www.yourmagento.com/news/
http://www.yourmagento.com/recipes/
http://www.yourmagento.com/tutorials/
All of these would be powered from 1 WordPress installation and integrated into Magento.
I've just changed my permalinks from /%postname%/ to /%postname%.html
So, links which are in /%postname%/ are showing 404 error.
I want to redirect those links to /%postname%.html in order to avoid 404 error page.
Changing the permalink settings with extension will effect only in posts, not in pages. In many instances like this I always use this plugin http://www.introsites.co.uk/wordpress/html-on-pages-plugin.html, it is a short plugin and editable, you can change the extension (.html) to many other like: .asp, .shtml, etc.
But please note: if you do an edit to your permalink setting please deactivate the plugin and activated it again when your done. Because if you change the permalink setting and didn't deactivate and activate this plugin all the page will appear as not found.
You can see the plugin stats http://wordpress.org/extend/plugins/html-on-pages/stats/ to see how many people used the plugin.
I'm working on migrating a static site to a new one based on Wordpress as a work platform.
The old site contains static html pages and a separate folder for the blog.
As a result I get the following URLs www.mysite.com / blog / category-name / post-number-one.
On the new site, WordPress turns the URL into www.mysite.com / category-name / post-number-one, removing the blog/ part.
For the sake of SEO, I must keep these urls like the old site. Is there a way using Wordpress to maintain this structure for blog posts only?
Yes, in the Wordpress admin, go to the Settings Tab, then the Permalinks menu. There will be a section called "Category base". Add "blog" there.
That should make it so the blog the categories are prefixed with /blog/category-name/post-number-one.
I had a similar issue. Basically I was running two Wordpress installations. One for pages and one for blog. Long story behind that.
But I eventually I needed to merge the WP installations.
In my case I also needed to go to Settings -> Reading and set the Posts page to "Blog", which was an empty page I named Blog also. This made it so the blog would be viewed at http://mydomain/blog/. I'm not sure if you wanted that too.
But yeah for the categories, you just need to add "Category base" under the permalinks setting.
in your general settings, you can set a subfolder as your url, which can be hard to debug when you have problems, in my experience.
the other is that if you go into your clean urls settings page, you probably can simply add a string before your other %params%
Is there any way we can have two different Permalinks in a Wordpress blog? This is because lot of us starts blogging when we have limited knowledge of SEO and end up in some URLs which are not that SE friendly.
Hence lot of pages from Blogs are already indexed by search engine and we do not want to spoil old URLs.
Thus I want to create new Permalink that is different than the old one. Only the newer post should use this permalink.
Is there any solution to this problem? Without 302 redirect we want to create 2 different Permalinks in the same Wordpress blog.
If I understand you correctly, you want to access the old posts only with the old permalink structure (e.g. ?p=123), and the new posts only with the new structure(e.g. /2009/08/name-of-article).
I'm afraid this is not possible without rewriting the Wordpress code (see short explanation at the end of my answer).
However, I think that Scott Yang's permalink redirect plugin (scroll down to FAQ) or Dean Lee's permalink migration plugin could be a solution.
Edit: both sites no longer exist. There are snapshots on Archive.com:
Scott Yang’s plugin, Dan Lee’s plugin.
These plugins are over 10 years old, however. The WP Redirect Permalink plugin might provide a similar service.
When Wordpress generates a link (e.g. for a new article, for "continue reading" links or for search results), it will use the new permalink structure, even for the old posts (which sadly isn't exachtly what you intended). If someone however uses an old permalink, it will be rewritten on the fly and the user (or SE) will be redirected to the correct page.
This 301 redirect should keep your page rank.
Explanation why having different permalink structures for old and new posts in parallel would mean changing Wordpress code:
For each post, Wordpress stores an unique ID (e.g. "123") and not necessarily unique post name (e.g. "name-of-article") in the database.
When an URL with a permalink like /2009/08/name-of-article is accessed, Wordpress translates this according to the currently configured permalink structure. If it constructs a link, it also does this according to the currently configured permalink rule.
You would need to add code toe Wordpress so that it uses two different rules depening on the age of the article.