[Solved] WordPress Shortcode Manager Plugin UTF-8 Issues

I love using ShortCode Manager in the Wordpress to handle extra content that is unique to my situation. It allows me to code PHP and dynamic content in the shotcode and use it on WordPress page or post.

However, the Chinese characters in the ShortCode just become garbage and bunch ? mark.

Codeigniter Shows Blank Page PHP + MySQL + Apache + Windows 7

Recently, I started a new development on one of my laptop running Windows7. I install PHP 5.3.6, Apache 2.2, MySQL 5. I move all the source code that was previously developed based on CodeIgnitor 1.7.

Problem

It shows blank page when I load the site on my laptop's localhost. 

Solution

Well. The solution is farily easy. If Codeigniter can not detect the mod_mysql module in PHP when the page is loaded, it doesn't return any error message.

• So you need to make sure you enable the mod_mysql in your PHP.ini file.
• Also make sure your .htaccess file is redirect correctly, if you are using Search Engine Friendly URL. Make sure mod_rewrite module is enable in your Apache httpd.conf file.

It's just that easy! A simple check will save you lots time. 

CodeIgniter Cache Issues

Well! This is actually not an issues of CodeIgniter cache system. It's how I wrongly use the cache function.

Whenever you use db->cache_on() function to cache the current query. It will cache all the executed queries from this point for the rest of queries in the whole PHP page.

In other words, it will cache everything query that do not have db->cache_off(). WOW! What a big mistake.

So if you just want to cache the current query execution, remember to put db->cache_off() after executing the query. Always remember that!

for example:

$this->pf_db->db->cache_on();
$result = $this->pf_db->db->query($query);
$this->pf_db->db->cache_off();

Without the cache_off(), all the queries after this one will be cached!

Annoying bug in MYSQL 5.0.51b

Just realized that in MYSQL 5.0.51b, sorting data from INNODB on primary key with where clause will NOT work.

See other bug report at http://bugs.mysql.com/bug.php?id=31001

Basically, if you use where clause in the query like this. The primary won't sort.

SELECT * FROM (`store`) WHERE `publisher_id` = 1006 ORDER BY `store_id` desc

In the query, store_id is the primary key in the innodb.

If you remove the where clause, it will sort correctly.

WTF! This is a critical bug. How come MySQL don't catch that at first place. This bug seem to be there for a long time.

PHP5 + Apache2.2 + MySQL5 Installation issue solved

I have tried many ways to get this working.

When install PHP5 + Apache2.2 + MySQL5, it shows that MySQL extension can not be loaded.

I followed every instruction to enable the extension in PHP.ini and point the Extension_dir to the right directory (ex. C:\PHP\ext). I also add the right model in Apache2.2 conf file to load the PHP5.

Problem:
PHP5 is unable to find the libmysql.dll and related MySQL extension. According to new PHP5 installation manual, you simply add your PHP5 installation path to the windows environment variables. Even you add your PHP5 installation path to the windows PATH environment variable, it still doesn't work.

Solution 1:
Copy libmysql.dll to your Windows System32 folder and restart your Apache2.2.

Warnning: This is not an ideal ways to solve the issues. You will run into situation that you need copy more dll to System32 folder. It is a night maire to upgrade the future versioin of PHP.

Solution 2:
After you set the PATH environment and restart your computer, it should just work without copying files to System32 folder. This is the reason, why it doesn't work.

Apache does not update the PATH environment until you reboot the server.

After you set the PATH environment variable, turn PHPINFO() and see if the Apache Environment variable is updated with the new path variable. If not, you will need to reboot the machine.

Problem solved! It's as simple as rebooting the machine.

MySQL Administrator :: server service or the configuration file could not be found

After install MySQL Administrator GUI tool, it is possible that you run into the error like the following when you login into the tool.




The solution is simple. Try login to the server without the login and password.


Remove the username and password and press control key. The "Cancel" button turns into a "Skip" button.

Press Skip and it will take you to the interface that you can manage and make correction to the config file. In most of the case, the default ini file is pointing to my.cnf. Change it to my.ini.




Problem solved!

MySQL 4.0 Fulltext search

Now FindyPages.com has added the fulltext search features for searching pages. It creates a better search results on page keywords, page description, page name and page url.

However, as far as I can tell that MySQL 4.0 is having some restriction on the fulltext search.

Restrictions

A few restrictions affect MySQL FULLTEXT indices. Some of the default behaviors of these restrictions can be changed in your my.cnf or using the SET command.

• FULLTEXT indices are NOT supported in InnoDB tables.
• MySQL requires that you have at least three rows of data in your result set before it will return any results.
• By default, if a search term appears in more than 50% of the rows then MySQL will not return any results.
• By default, your search query must be at least four characters long and may not exceed 254 characters.
• MySQL has a default stopwords file that has a list of common words (i.e., the, that, has) which are not returned in your search. In other words, searching for the will return zero rows.
• According to MySQL's manual, the argument to AGAINST() must be a constant string. In other words, you cannot search for values returned within the query.

select count(members_pages.pageid) as record_count
from members
inner join members_pages on members.memberid = members_pages.memberid
where members.status_access = 1
and members_pages.status_access = 1
and members_pages.status_viewable_by = 1
and (
MATCH(members_pages.page_name, members_pages.page_keywords, members_pages.page_desc, members_pages.page_url) AGAINST ('" . trim(strtolower(addslashes($keywords))) . "' IN BOOLEAN MODE)
or lower(members_pages.page_url) like '%" . trim(strtolower(addslashes($keywords))) . "%')";