Do not know if it's just me wishing it but it looks like the WP team is working towards allowing high unicode characters URL:erna
Jag gjorde uppdateringen idag till 3.1 and had been robbed of getting to spend a half hour to get my URL:s at work again but to my great surprise, translated WP my old URL:s correct to % encoded URL:them.
Unfortunately it does not translate WP URL:leaving from the title is automatically, and, enter a URL with Å Ä or Ö they will be translated to aao, However, you can now enter the % coded equivalent and get the expected result.
I will take and look at the code in the near future and see what he found on.
Now that I've been playing with WP for a while, I feel I have begun to find the plug ins that I actually think is worth using.
Less is more
I tend to think that less is better, less to keep track of less that can go wrong, a risk of mixing plug ins anyway is that there may be compatibility issues between them, and large (non-standardized) fremeworks has also a tendency to destroy some, so therefore it is here to choose with care, and one should be aware that it is very difficult to find a general solution that works in all, or in most cases.
In a race where all are equal, and you do not want to cheat (link the), you have to trim their site to the teeth, certainly there is some functionality you want to keep, and eye candy, and here you have to make a choice: Should I transcode my eye candy so that it can withstand being compressed or should I sacrifice a certain amount of bandwidth to be able to update without any problems?
So we want to minimize loading times for our site, and avoid our URL:s break, then we really 4 pc tools we can use:
Cache Ning – a technique to cache generated HTML code in order to not be needed when calling.
Kodkomprimering – to delete any unnecessary “white spaces” and kommentaret in the code that leaves the server.
301 – redirects – Telling clients that a resource has moved.
What we want to avoid is core hack in WP, the risk is that we may pick on the next update, and we want juh make things easier for us.
Do we start with our modules before you fall asleep in front of the screens
301 – redirects
The reason we want to automate our 301 redirects is that sometimes we want to make major changes to our site structures, and chasing loose URL:s is both time consuming and tedious.
There are two different plug ins that I would use for this, one is for the lazy and the other for those who want ka full control of their 301:s and 404:or
Permalinks Moved Permanently (for the late)
This is a great plug-in that works great as long as you do not want to change the name of an article. This plug-in works in this way to the right before 404 takes to do so on a 301 repositioning based on the information in the URL tokenet:in, ie if you have 2p entries with the same name under different categories (or similar) so there will be a conflict.
This plug-in is what I would recommend every person who is serious about their 301:s and 404:or.
One can t.om put it on to monitor your articles and make automatic redirects when the article URL change.
This plug-in is not recommended for beginners, However, it provides a very good control on all redirects.
Minify, kodkomprimering and cache.
Until not so long ago, I used different tools for this, but today it has been a really good tool that gives a very good control of all these parameters.
W3 Total Cache
This is a plug-in that at least I'm really pleased with, except that it fixes caching so you can choose how it will cacheas for each component. the three storage methods are opcode, memcache and disk.
If one can avoid the disk cache, one should do it when the dishes are very lånsammare is working memory.
Here you can also play with different minify and kodkomprimerings tactics. I highly recommend disabling the cache when you play with these, This is just to test themselves until the moment you discover that your plug ins stop working.
Besides these, it is a plug-in I can not live without wp-insert. This plug-in is really to in order to be able to add custom elements trust every one wants in their templates such as advertising and banners, but besides this, it also gives syntax-high lightning in the internal editor for templates and plug ins, which is very appreciated by me.
Is there any plug ins that are worth mentioning that I missed?
I wanted to restructure the blog a little firm wanted to get me some relationships that were already set to reduce the work a little, the first thought that occurred to me was to convert some old labels to categories.
There are juh lots of plug ins for WP
There are very many plug ins for WP, but for some strange reason it never seems to be something that does just what I want, so then it was just to hack a little concerning.
Happy Controversy I have rooted a bit in the database to WP part now so I found quite quickly what to do.
However, there is a small pitfall here, ensure that you do not have a category already named it as the label name.
Ok, hur it appears?
There are three tables that are of interest here, though only 2 which we will use. But I have the nature that I would like to know how things work so…
wp_terms – This table is a list of terms or and their slugar, and an id.
wp_term_relationships – The relationship between terms, and other items.
wp_term_taxonomy – vilken typ or “taxonomy” the term belongs
OK! With that in your back pocket as we head into what we want to do, and it is to change “type” to view terms, and to do this we need to know which id a term has.
What we do is simply looking up the term in the table wp_terms, notes “term_id” for the terms that we want to change.
The next step is to simply look up the latest in wp_term_taxonomy in term_id field, then we will replace taxonomy from post_tag the category and just like that we have converted these categories!
next time you log in, you will find these categories in the category tab in WP.
I take no responsibility for World War, the cat gets pregnant, girl leave you, scolding of mother, data explodes, or other side effects this may have, it is entirely up to you to weigh and take risks.
Hope this helps someone anyway!
Ok, then it was time again for another update.
I helped Niklas Lindh to get to the, ä and ö in their slugar little earlier to discover that the new update to wp 3.0.3 pajjade the entire.
For those who are interested to keep up with, filen man core hackar i är /wp-includes/formatting.php, instructions can be found on a previous post on this blog.
There are many who have gone out and the claim that WordPress is the best thing that has happened to the web and it is the best for SEO.
Something that is important to realize is that the search engine does not care what system you have behind, but the only thing that is important "on page" is the output that is served to the robot. The search engine is really a web client like any other, and must follow the rules set by the http protocol and languages html / xhtml to determine what pages all about.
I tested WordPress now for a little while and I have come to both positive and negative findings on the WP.
Easy to use for end users
easy to use templates
Pingback / trackback
With the right plugins WP is very good to work with the right plugins, there is support for most of what I really want to do.
One can easily get syntax highlighting lightning in the built-in editor and file user.css is a good solution to over Ridea default values in the template using.
Pingback / Trackbacks are an effective way to create back links if blogs.
Absolute URL:in the database
large inkopatibilitet between versions
no hierarchical structure of content pages
The first major problem I encountered with WP was when I was moving it between sub-domains. Any URL:you are hard-coded in the database with their absolute values, which can mean some pretty big problems when moving the site from one domain to another.
The other thing I reacted to was that WP forces one to not use the, ä or ö in URL:erna, However, working characters such as é, £ and €, and crylliska alphabet, This suggests that the developers had not thought of that some want to use the, ä and ö in their URL:them.
Then they forgot to exclude the other characters as the way of thinking would mean problems for some browsers.
I would like to see a solution that allows all characters but 301:is the normalized form of the path to the real, eg / Nails → / false nails.
That there is a hierarchical structure between content pages is hugely frustrating for me.
I want to work in such a way that I will be able to create large structures and be able to write content on the parent page and any other content on Childe, to create and Logical skalblara sites.
Then another annoying thing, one of WP's strengths is also one of its weaknesses, pluginsen.
There is a huge variety of plugins, a real jungle, and a plug that was masterful in a version of WP, may not work in the next.
I would like to say that WP deserves praise, but is far from flawless. Although it is an easy to use system which suit many, the system has clean design error (programming / structured databas), if one were to ask me.
A request from me would be to simply be able to create hierarchical structures, also “sidor”, and to be able to have content in each level.
But I would not discourage anyone from using WP, it is a good system for the end user and it is possible to create much in the, but one should also be aware that there may be a problem for a domain change, or whether to switch servers.
Each system has its pros and cons and one should choose platforms based on the needs that the project has.
But as I say, there are no universal solutions, one size doesn’t fit all.
Better late than never, they say, but this update was awaited!
Vtiger 5.1.0 had was good but…
Vtiger 5.1.0 was good but there was a big problem that I think they've lost a lot of users on, is that it was not compatible with PHP5.3, Now, it was so that there was hack to get around this, but it was not the easiest to fix.
No one wants to maintain its servers out of date as long, and finally, this update that supports PHP5.3 “out of the box”!
The developers have not been idle…
There have been several good news with this release I will just list a couple of news…
sms notifiering (via extern provider)
This allows b.la that you can send text messages to their customers, that there is an iPhone and an Android app to the system.
Then I want my SEF:s with å, ä and ö, I was inside and fulhackade bit of code.
This, I would not recommend anyone to do, it is a quick hack and not directly thought, but I want them here SEF:why now and why I do it, may take and look at what the code does little more thoroughly later.
WARNING, these changes may be lost at the next update, I would appreciate someone who can do the WP plug-ins could watch this, but now we know where we must begin in all cases.
Now I have not checked so thoroughly, but it seemed that everywhere where cunning and title were handled, anroppade judgment function sanitize_title($string) which according to the documentation only to strip off php and html characters from the title, and if this does not work, it shall return a default title, if set.
In this function I found this row :
$title = apply_filters(‘sanitize_title’, $title, $raw_title);
It calls another function in WP called “apply_filters”, “apply_filters” running different filters that are globally declared in an array, seems that, marked with a tag, ettikett, the fall called 'sanitize_title'.
Now I have not time to look up where the filter is declared, but I was lucky but me and found a function directly below the name:
I have not found any call to this function yet but it seems basically do what I want, except for one small detail where the aropar one anna function to remove all the accents from the title / URL:en
Så jag bytte helt enkelt ut $title = apply_filters(‘sanitize_title’, $title, $raw_title); med $title = sanitize_title_with_dashes($title); and commented out the line $ title = remove_accents($title); i sanitize_title_with_dashes($title).
Now I do not know what other side effects this may have, and I recommend no one to do it this way.
the correct solution to this problem should be to find out where the filter 'sanitize_title’ declared and write a plug-in that byer out this marking label.
but as I was told, I do not have time, but I hope that this can lead a pug in wp writer on track.
Hello Friends, hello friends.
As nine Kansk see in the SEF:one to this so take WP krylliska characters, and these are correctly translated into their url encoded counterparts.
The same goes for other special characters like £ € ¥ ß æ ł ł đ which I think seems to be a bit funny by WP-team, Also Danish ø goes through.
Basically, “best practice” be to print UTF-8 Sephar and 301 their circumscribed variant to UTF-8 sefarna.
ex: mindoman.se / blaa> mindomän.se/blää
Detta kanskeMönsterås should learn from
And yes, I know there is a difference of domain and path, I'm just trying to illustrate a principle.
To go a little against the grain again, I now try to get to the,ä and ö in wordpress shrewd:would.
Contrary to the general recommendations out there, I am fully convinced that Google actually interprets international characters in the paths correctly today.
That this applies to domain name today called IDNs are becoming more accepted, which even I agree.
Anyway, try a search such as this, where we see that the word Assassin is boldat in search results for example wikipedia.
Sat for a while last night and looked through the code and database structure in WP3.1 and did some tests, and there seems to be a little harder than I thought from the beginning.
However, I would not hack core WP nor, then all my changes disappear during an update.
Does anyone know of a plugin that fixes this?
After working with the site so far I switched now to WP, migration was relatively painless, but i lost all my comments, although so many were they not in all cases.
Hope Vist I will be better able to maintain the site and my primary goal is still to write articles, but may take it as time.
I'm pleasantly surprised anyway how easy the migration has gone, and it will be fun to see how hard I can SEO:a denna site nu.