11.10.06

Issues with WordPress’s Rich Text Editor

Posted in Blogs, programming, technical at 1:26 pm by spryken

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/wpg2/wpg2embed.inc on line 1229

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/wpg2/wpg2embed.inc on line 1245

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/stats/stats.php on line 371

As I was trying to include the code snippet for my hack to automatically generate WML from a WordPress blog, I found out that even with the code plugins, the Rich Editor provided by WordPress strips the newlines from -pre- tags.

I had to edit the post in Preformancing, an extension for FireFox.  That or revert to the standard editor. 

I must say, that I have been extremely pleased with Preformancing.  It is browser based and open a “pane” below the browser tabs.  That way I can reference the page I am quoting or blogging about without having to switch windows.  Very handy.

Technorati Tags: WordPress, Blogging

powered by performancing firefox

Permalink Comments 1,749 views

A Scout’s Campfire is WAP Friendly

Posted in Blogs, BoyScouts, programming, technical at 1:19 pm by spryken

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/wpg2/wpg2embed.inc on line 1229

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/wpg2/wpg2embed.inc on line 1245

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/stats/stats.php on line 371

I have implemented my WordPress hack for WAP enabling WordPress blogs on A Scout’s Campfire.  I will continue to monitor and update the WAP capality as I discover issues or improved plugins.

Technorati Tags: Blogging, WordPress, WAP

powered by performancing firefox

Permalink Comments 1,466 views

11.09.06

Hacking WordPress to Automatically Generate WML for WAP Devices - Part II

Posted in Blogs, programming, technical at 7:42 am by spryken

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/wpg2/wpg2embed.inc on line 1229

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/wpg2/wpg2embed.inc on line 1245

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/stats/stats.php on line 371

Well, I finally was able to hook up with Bob Porter to do some testing…… I cannot say I was pleased with the results. The very same redirect codes that work in a stand alone script were not working. The only difference was the “IF” statement to determine if the browser was WAP enabled.

After a day of email communication, we finally got together via phone. Then it was about a 1/2 an hour before I had the AHA moment.

We have successfully tested the automatic discovery of WAP enabled devices!! At least for Windows CE based devices. So, I am declaring success.

If you have some other WAP device, please test it here and let me know the results.

Here is the index.php that I created to replace the one provided by WordPress… If you use it, you will have to modify the location you redirect to.

<?
$pos = stripos($HTTP_ACCEPT, "VND.WAP.WML");
if ($pos === false)
{
 
 $pos = stripos($HTTP_USER_AGENT, "WINDOWS CE");
 if ($pos === false)
 {
  define('WP_USE_THEMES', true);
  require('./wp-blog-header.php');
  exit(0);
 }
 else
 {
 header( "HTTP/1.1 301 Moved Permanently" );
 header( "Status: 301 Moved Permanently" );
 header( "Location: http://www.spryken.com/blog/wp-wap.php" );
 exit(0); // This is Optional but suggested, to avoid any accidental output

 }
}
else {
 header( "HTTP/1.1 301 Moved Permanently" );
 header( "Status: 301 Moved Permanently" );
 header( "Location: http://www.spryken.com/blog/wp-wap.php" );
 exit(0); // This is Optional but suggested, to avoid any accidental output
}
?>
  

Technorati Tags: wordpress, wap, blogs, programming, php

powered by performancing firefox

Permalink 1 Comment 2,605 views

11.07.06

Hacking WordPress to Automatically Generate WML for WAP Devices

Posted in Blogs, programming at 12:09 am by spryken

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/wpg2/wpg2embed.inc on line 1229

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/wpg2/wpg2embed.inc on line 1245

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/stats/stats.php on line 371

I was exploring some plug-ins for WordPress, looking for a Post Hit Counter or a stats plug-in, when I ran across wp-wap by GaMerZ.  It provides WordPress with the ability to deliver pages in WML for WAP enabled Mobile Devices.  Great I thought.  I will make A Scout’s Campfire wap friendly.  I created a sub-domain and put a redirect php script in it, pointing to the wp-wap.php.  Since I don’t have WAP enabled mobile device, I contacted my buddy Bob Porter.  Both he and I got prompted to save the file wp-wap.php when we hit the new sub-domain in FireFox and IE.  Puzzled, I suggested he try with his smartphone.  Lo and behold, it worked correctly.

We deduced that both FF and IE could not handle the mime type WML.  A little digging on the web revealed ways to detect WAP enabled devices and redirect accordingly.  WAP and domain names,  provide a starting point for me to build a replacement for index.php in WordPress.  Using information from that site and IEMobile Team Log, I was able to modify the index.php to query for WAP devices and redirect to wp-wap.php while allowing any other devices to process normally.

At least I think that’s what I did.  Bob is off-line currently, so I can’t test the WAP device, but FF is working correctly.  I have enabled this on this site only.  If further testing holds up, then I will be adding it to A Scout’s Campfire.

Look for an update tomorrow.

Permalink Comments 1,427 views

04.19.06

WordPress Update and Widgets

Posted in Blogs, programming, technical at 1:31 pm by spryken

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/wpg2/wpg2embed.inc on line 1229

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/wpg2/wpg2embed.inc on line 1245

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/spryken/www/www/blog/wp-content/plugins/stats/stats.php on line 371

I have completed updating my WordPress installation to version 2.0.2 and adding the Widgets plugin.  That necessitated my upgrading my theme.  In the process, I experimented with serveral other widget-enabled themes, but came back to Ocadia.  It appears to work the best in both IE and FireFox, and to handle the most widgets.

As always, let me know if you see any strange behavior.

Permalink Comments 536 views