Forum Moderators: Robert Charlton & goodroi
[edited by: g1smd at 4:26 pm (utc) on Nov 2, 2012]
I disagree about wp making those urls...figuratively it does with the rewrite and without a redirect.
There won't be duplicates nor stemming. If I create a wp page that says sample.html...only that is served. Not sample.htm nor sample (the latter two result in 404's assuming the .haccess is configured as I showed).
Sure, this can be done. If you know what you are doing, you can achieve just about anything with mod_rewrite.Not to be nitpicky...but this isn't some run of the mill hack. It is the official recommended implementation from wordpress and is very common (any wordpress site that doesn't have index.php prefixed in the urls is using this).
I have to manage a redesign of old static sites and their pages have .html-Urls. As the new CMS will be Wordpress and WP doesn't allow .html-Urls for pages I think about a 301-redirect.
add_action('init', 'my_page_permalink', -1);
function my_page_permalink() {
global $wp_rewrite;
if ( strstr($wp_rewrite->get_page_permastruct(), '.html') != '.html' )
$wp_rewrite->page_structure = $wp_rewrite->page_structure . '.html';
}
this isn't some run of the mill hack. It is the official recommended implementation from wordpress
We've discussed the many deficiencies in that "standard issue" Wordpress code many times before, the last being only a few weeks ago. Do not use that code in its present form.
index.php in the url: Is that something I will notice with my eyes when creating new pages or something going on in the background of WP
There are some reasons why "static made" posts are not a good idea, for example, when adding an onsite-blog. Of course ecerything can be fixed anyhow, but I'm not a coding expert and like things simple and efficient.
Besides my pages are pages and Google should identify that correct in the code, not reading there "post" blabla.
I believe indyank's code still depends on the .htaccess implementation as again there is no way for wp without the help of apache/.htaccess to implement url rewriting.
Creating and editing (.htaccess)
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
As for pages vs posts...I think you are right to uses pages.
index.php which does the grunt work in making almost any url structure you want work.
Once you have about 50-100 static Pages or so, and you’re using an ambiguous custom structure, then the system tends to fall apart. Most of the time, the ruleset grows too large to fit into a single mySQL query, meaning that the rules can no longer be properly saved in the database and must be rebuilt each time. The most obvious effect when this happens is that the number of queries on every page load rises from the below 50 range to 2000+ queries, and the site slows down to snail speed.
Are you sure you only want to migrate your static sites to "Pages" in wordpress? Why not Posts?
Nobody shares this feeling using a Url-migration-tool in order to keep up the Urls?
htaccess can never "make" a URL.
I disagree about wp making those urls..
That code does nothing for .html URLs.
that will work for .html urls
The .htaccess script (which is common not only with wordpress ( [codex.wordpress.org...] ), but with drupal and other CMS'es),
doesn't mean it's good code.
What WP is doing is SERVING CONTENT from one location while pretending to live at a different location.
The only thing you can use an identifier for is to refer to an object. When you are not dereferencing, you should not look at the contents of the URI string to gain other information.
For example, within an HTTP identifier, even when access is made to the object, the client machine looks at the first part of the identifier to determine which server machine to talk to and from then on the rest of the string is defined to be opaque to the client. That is the client does not look inside it, it can not deduce an information from the characters in that identifier.
Once you are in WordPress, the "real" underlying name of the page isn't html any longer though is it? It's .php.
[edited by: Robert_Charlton at 7:58 pm (utc) on Nov 5, 2012]
#4516013
/url1/url2
