February 8, 2007 in the early morning
· Filed under CMS, apache, email, fedora core linux, gmail, google, information security, linux, live journal, postfix, wordpress
Yesterday I noticed a new comment added to an older post on Blix theme bug in sidebar.php, when I navigated down dashboard/Manage/Post/edit to update the live jounal of this wordpress press blog server. The comment was left a day ago and I don’t recall receiving an notification on it. In the past, I receive email alerts for comments added to posts on this server and others. Surprised as I am, I checked around. It turned out Gmail now decides notification emails from this wordpress server are spam emails and promptly drops them into the SPAM filter. Read the rest of this entry »
Permalink
February 2, 2007 late at night
· Filed under CMS, tiger-admin, wordpress, wordpress plugin
I had been using tiger-admin 3.0 without any problem since Wordpress 2.0.6 and 2.0.7. The server was then upgraded to Wordpress 2.1 the first day it became available, with all plugins disabled prior to the upgrade as instructed by wordpress.org. Initially I had problem with visual editor mode and timeofday plugin. The visual editor problem was resolved quickly. Only last night I got around to re-enable tiger-admin wordpress plugin. The administrator dashboard looked pretty again. Yay! I was happy. Off I went, to bed.
Tonight, when I was updating a static page on how to secure wordpress server and other LAMP servers, the editor gave only a half-width window instead of the full-width window. The WYSIWYG editor mode or visual editor mode works fine. With the half-width window, it is rather clumsy to identify and to edit out a handful of extra <LI><UL><UL></LI> by hand. This is how it looked like:
These extra HTML tags were generated automatically by the VISUAL editor, by mistake, I guess. The extra HTML tag generation was triggered by a blockquote between unordered list items with a few attempts to indent/outdent (or promote/demote) list items. I believe visual editor in Google’s Blogger suffers from a similar problem. Under visual editor mode, I eventually reach a point that I can no longer promote or demote a line any more.
Even though it took me a bit longer to edit out these extra HTML tags, I decide to leave it alone. Rarely I need to edit in code mode anyway. Otherwise, why use a CMS?
Later I tried to identify 404 links reported by Google webmaster tools by searching the URI elements from manage/post and manage/page. The search form is somewhat misaligned and returned nothing, when I know at least one of the post or pages should have showed up. At that point, I decide to deactivate tiger-admin to verify whether it is to blame. Sure enough, once tiger-admin 3.0 is deactivated, the search form looks normal and returned results as expected. Of course, now the code mode gave full-width as well.
hmm… I thought Wordpress 2.1’s release page has tiger-admin 3.0 listed as fully compatible. Anyone shares similar problems?
Permalink
January 29, 2007 at around evening time
· Filed under CMS, seo, site_news, wordpress, wordpress theme
So far, most of the traffic to this site was referred by Google Search or alike. More often than not, readers land on a single post. I believe a list of recent posts would appeal more to the readers to hang around than the current page list. This site uses SEO Dave’s almost-spring-adsense theme with a few of my own tweaks. Almost-spring-adsense theme doesn’t have post list at all, while the Blix-adsense theme does. Read the rest of this entry »
Permalink
January 27, 2007 in the early evening
· Filed under CMS, site_news, wordpress, wordpress theme
A Google AdSnse text link is added to the top of the page, right below the blog title. Look at top of this page, you shall see it. The stying and such is a copy+paste of SEO Dave’s Google Adsense unit code from page.php into header.php, in his famous adsense-spiked almost-springs wordpress theme. Read the rest of this entry »
Permalink
January 25, 2007 at around evening time
· Filed under CMS, fedora core linux, information security, linux, wordpress
Under wordpress 2.1, uploading options is set under Options/Miscellaneous. The option name is probably a misnomer, since it is nothing else but uploading options. Anyhow, therein default directory to store upload is shown as /wp-content/uploads. However, when I uploaded an image file from the visual editor, the picture ended up under /wp-content/ directory on a wordpress 2.1 server just upgraded from wordpress 2.0.7 on Fedora Core Linux 6. No ‘uploads’ directory is there either
Read the rest of this entry »
Permalink