umquat

I installed and removed it in less than 5 mins.

It felt like killing a mosquito with a photon torpedo! that plugins is soo huge that I wouldn’t know where to begin!

—————-
Thanks webs!

I’ll install it and report back ??

Okies, I’ll post it over there ??

I tried to get it working, but failed :-(. I’m using 1.2
It complains a lot about failing to include(), but after fixing that, the plugin headers are all wrong, so it won’t show up properly in the plugin control page.
After fixing that, my PHP started to complain about parse errors on a perfectly formed line. (line 27, the title)
any ideas?

Anyone working on this? one engine, many front-ends?
If I wanted to start coding suchs athing where would I need to start? who would be the WP developer most interested in such a feature?
Best
Rub??n

woops, double post, I thought edit did exactly that ?? Please delete the ugly post ??

ala_747, michel_v: UTF-8 is better, so I needed to convert the mysql dump to UTF-8. In Linux there’s a nifty utility called iconv.
This is what I did:

iconv -f iso-8859-1 -t utf-8 ../blogdump_wp_1.0.sql >blogdump_wp_1.0-UTF8.sql

Then I could feed it it Mysql, worked like a charm.
I think the moving to UTF-8 is a very solid decision, but the upgrade script really should take care of that. I would suggest the following steps:

1. Dump the DB to a file
2. If in Linux, use the systems iconv to convert encodings
3. for Windows users, provide the instructions to download and execute iconv.exe (maybe from https://www.zlatkovic.com/pub/libxml/iconv-1.9.1.win32.zip) Maybe bundle it if licensing permits
4. create another database, preferably with another user and passwd
5. feed the newly converted file to mysql, using the new database and user
6. Run the current upgrade (modify structure, etc.)
7. Ask if the source code will use the current location, or another one

Hope it helps
Cheers
Rub??n