Thread Starter
Kassad
(@kassad)
Well, I figured it out, at last.
At the end of the script, in the <h2> tag, the apostrophe in the name was not escaped and effectively killed the plugin. Now, it works as expected 🙂
Though, I ran into another problem. My wp uses utf-8 with iso-8859-2 collation and the posts transferred to punBB appears as unencoded utf-8.
I wonder, if it could be circumvented, anyhow.
Now, if you combine it with the liewcf/almosteffortless integration hack and you cannot escape comment spam otherwise then you have a real alternative.
Thread Starter
Kassad
(@kassad)
This is not a bump 🙂
I would need some professional assistance.
I have got myself into a mild argument with people at the punBB forums regarding this plugin.
They thought my “fix” to be useless, I suppose due to my improper explanation. Though, they missed the point that it worked. I put the plugin up into my open space, here:
WP2punBB Plugin
in the directory WP2punBB.
At the end of the script, there is a div class=wrap section with the incriminated apostrophe.
I kindly ask you for a professional explanation how this affects the underlying code and what is the proper wording for it.
http://love-unlimited.net/test/WP2punBB/
gets a 403 Forbidden.
If you are showing actual code, a .phps or .txt file is better, or publishing it at pastebin.
