There are some issues with WYSIWYG editors besides HTMLAREA, but even this one doesn't load if the Blog's language is set to spanish.
I have tried FCKeditor and TinyMCE without success... I been able to use them at some point, but not without an extra effort and lots of searching on the forums.
Perhaps setting other default HTML editor besides HTMLAREA could be a good idea.
@Andrew: Password protection comes with the "Extended Properties fo rentries" plugin.
@Raimondo: Can you elaborate on the "more powerful rewrite control"? What is insufficient in the current method?
@reinhardl: Why an additional Wiki? What's wrong with the current one?
@Mandrake: Added the URL rewrite for tagging to the Todolist. About Caching, I simply need more developers for help and ideas on this. Same goes for Fantastico, I have no experience with it. About your shortened variable: You can use the |@truncate smarty modifier on the entry.body variable. Setting categories via potfetcher in the mail subject is already possible. I added tags to the todo list.
About the spanish language file from HTMLArea: I would need a spanish developer to check this, I don't know what's wrong inside the file, probably some UTF-8 clash.
I believe this is more a task for Postgresql 8.1.x to clean up this mess. Withdrawing typecast support sucks, I see no way to make s9y properly support this scenario. s9y depends on dynamic typecasting. This is actually a feature of a RDBMS, I see no reason to be so pedantic to remove this. It's like making PHP6 require full variable initalization and getting rid of flexibility.
Add a Favicon button . Simple! but would be cool to have in the admin area just to enter the url of the icon and s9y writes the entry in the index.tpl.
If the post is indexed well, search engines and other sites will still point to the old url. The old url should have a 301 redirect to the new url. This will prevent duplicate content problems since both urls will bring up the same content.
Mandrake am um :
Ehm, I almost forgot
There are some issues with WYSIWYG editors besides HTMLAREA, but even this one doesn't load if the Blog's language is set to spanish.
I have tried FCKeditor and TinyMCE without success... I been able to use them at some point, but not without an extra effort and lots of searching on the forums.
Perhaps setting other default HTML editor besides HTMLAREA could be a good idea.
Garvin am um :
@Andrew: Password protection comes with the "Extended Properties fo rentries" plugin.
@Raimondo: Can you elaborate on the "more powerful rewrite control"? What is insufficient in the current method?
@reinhardl: Why an additional Wiki? What's wrong with the current one?
@Mandrake: Added the URL rewrite for tagging to the Todolist. About Caching, I simply need more developers for help and ideas on this. Same goes for Fantastico, I have no experience with it. About your shortened variable: You can use the |@truncate smarty modifier on the entry.body variable. Setting categories via potfetcher in the mail subject is already possible. I added tags to the todo list. About the spanish language file from HTMLArea: I would need a spanish developer to check this, I don't know what's wrong inside the file, probably some UTF-8 clash.
Holger Mitterwald am um :
Full PostgreSQL support. Postgresql 8.x has messed up a few things. Would be nice if they could be corrected.
Garvin am um :
I believe this is more a task for Postgresql 8.1.x to clean up this mess. Withdrawing typecast support sucks, I see no way to make s9y properly support this scenario. s9y depends on dynamic typecasting. This is actually a feature of a RDBMS, I see no reason to be so pedantic to remove this. It's like making PHP6 require full variable initalization and getting rid of flexibility.
Alex am um :
Add a Favicon button . Simple! but would be cool to have in the admin area just to enter the url of the icon and s9y writes the entry in the index.tpl.
Kevin am um :
The htaccess could be a bit more seo friendly i believe.
For example...
If I edit a post's title, it will change the url for the post.
domain.com/archives/1-old-title.html domain.com/archives/1-new-title.html
If the post is indexed well, search engines and other sites will still point to the old url. The old url should have a 301 redirect to the new url. This will prevent duplicate content problems since both urls will bring up the same content.