I decided to finally make the jump to some sort of information manager after a talk I had with someone at work today. When working for so many companies , managing so many devices, and being a member of so many web communities it is almost impossible to remember login information, IP information, and random other notes about every installation, web site, etc. I started looking for a solution where I could at least store devices, I could access this information from anywhere (at least on my Touch), and it was secure. I was pleasantly surprised by SplashID which will allow you to store all sorts of information in all sorts of ways. The best part is that when it boils down to it this information is going to be more secure in a solution like SplashID, which uses encryption that tops banks, versus being spread through out various notepads, documents, emails, and other places on numerous computers and possibly even on paper.Details
I got an error when trying to add postback triggers for the ScriptManager control in ASP.NET by using the UpdatePanel.PostbackControls.Add method and passing in the control’s id. In my situation, I had a GridView that was wrapped in an UpdatePanel and I wanted the edit column to trigger a postback and link to another page.…Details
I use the JPF Login/Out plugin to display text at the top of a WordPress site and after upgrading to WordPress 2.7 the logout link stopped working. After reading in the WordPress Codex it appears that the wp_logout_url was added to provide a nonce-protected URL that can be used during logout.
In the jpf_loginout.php file on line 17 change the below:
- $link = $before . '<a href="' . get_settings('siteurl') . '/wp-login.php?action=logout">' . $log_yes . '</a>' . $after;
You may run into issues installing the mysql gem on a Linux server running a 64-bit version of MySQL server. When attempting to install the gem its likely you will get errors if you don’t specify a couple options when running the command. The issue I continued to have was the options are clearly listed out and I felt, because of previous issues with 64-bit applications being installed, that I was using the proper options to move past the errors I was seeing. What I finally figured out was the fact that an extra “–” was required in front of the options.
Below I show the error in detail which will then be followed by the command to issue for a successful installation of the MySQL gem on CentOS (should work with any Linux server) running mysql-server.x86_64 or the 64 bit version of mysql-server instead of the 32 bit mysql-server or mysql-server.i386.Details
I received the below error when attempting to compile PHP to use with Litespeed as an LSAPI module. The error was related to multiple versions of numerous MySQL RPM packages being installed.
PHP Compile Error:
checking for MySQL support… yes
checking for specified location of the MySQL UNIX socket… no
checking for MySQL UNIX socket location… /var/lib/mysql/mysql.sock
checking for mysql_close in -lmysqlclient… no
checking for mysql_errno in -lmysqlclient… no
The PHP configure script was getting confused because of two 32-bit MySQL RPM packages being installed. If you look below this is the MySQL packages yum was showing installed on the server.Details