I assume that the problem is caused by Google Analytics, namely the "track outgoing clicks" feature (as recalled, might be inaccurate feature name). "Track outgoing links" adds some JavaScript code to all outgoing links, and that script has tick characters like this one ' which, incidentally, are also used for delimiting the values of comment anchor tags.

To fix:

1. locate file wp-includes/comment-template.php
2. in that file, find the get_comment_author_link function (lines 140-150 in WP 2.7.1)
3. replace the line
   PLAIN TEXT
   PHP:

   1. $return = "<a href='$url' rel='external nofollow' class='url'>$author</a>";

   with

   PLAIN TEXT
   PHP:

   1. $return = '<a href="'.$url.'" rel="external nofollow" class="url">'.$author.'</a>';

This helped me and might help you.

Two most common reasons (and fixes) for the MySQL server has gone away (error 2006) are:

1. Server timed out and closed the connection. How to fix: check that wait_timeout variable in your mysqld's my.cnf configuration file is large enough. On Debian: sudo nano /etc/mysql/my.cnf, set wait_timeout = 600 seconds (you can tweak/decrease this value when error 2006 is gone), then sudo /etc/init.d/mysql restart. I didn't check, but the default value for wait_timeout might be around 28800 seconds (8 hours).
2. Server dropped an incorrect or too large packet. If mysqld gets a packet that is too large or incorrect, it assumes that something has gone wrong with the client and closes the connection. You can increase the maximal packet size limit by increasing the value of max_allowed_packet in my.cnf file. On Debian: sudo nano /etc/mysql/my.cnf, set max_allowed_packet = 64M (you can tweak/decrease this value when error 2006 is gone), then sudo /etc/init.d/mysql restart.

If you get MySQL server has gone away (error 2006) when using MySQL ODBC driver - give this hint a try.

When right-clicking many links in FF3/IW3, it quite often happens so that a random action is performed instead of opening the context menu (bug report).

One of the solutions work-arounds (suggested by Andre Pirard) is to slow-right-click, that is to hold the right mouse button down until the menu actually appears, then - and only then - release it. Or, you can even slow-right-click, move the pointer over the desired menu item, and then release - that will perform the desired action in a single long right click (instead of more common single right click with a following single left click.)

Alternative workaround (found at the bug report page): install the mouse gestures add-on, and restart firefox. Tested: works for me.

This bug/behaviour is otherwise unsolved.

Update 2: fsmullin suggested a method to fix a similar error in index_table.php, the files_count_max cannot be found error when you click the FILES tab/menu item. His suggestion is now incorporated into the post.

Update 3: this post is still relevant for dotProject 2.1.3.

In one of my recent posts about project management software I stated the desire to extensively test dotProject 2.0.4. However, many shared hosting providers appear incompatible with dotProject: the right to CREATE TEMPORARY TABLES in MySQL is not granted, but is needed by dotProject.

Here's sample error (2.0.4):

query failed(CREATE TEMPORARY TABLE tasks_sum SELECT task_project, COUNT(distinct task_id) AS total_tasks,
SUM(task_duration * task_percent_complete * IF(task_duration_type = 24, 8.0, task_duration_type))/
SUM(task_duration * IF(task_duration_type = 24, 8.0, task_duration_type)) AS project_percent_complete FROM `tasks` GROUP BY task_project)

For 2.1.2, sample error would be:

Table 'tasks_total' doesn't exist

I tried looking for solutions, and here's what I found...

First of all, I tried issuing the "grant" command to try enabling temporary tables:

GRANT CREATE TEMPORARY TABLES ON dot_projects.* to dot_projects@x.myserver.com;

Expectedly, this didn't work: "access denied for user ....".

Then I tried looking for a ready-to-apply solution. Here are the links relevant to the topic, if you happen to prefer "the source", and not the retelling: link 1, link 2, link 3, and link 4.

However, none of the solutions described behind the links worked for me.

Here's my solution (error fix).

To fix, instead of creating temporary tables each time they are needed (what is impossible on many shared hostings), we need to create the necessary tables once. Then, instead of dropping temporary tables, we just truncate our "static" tables.

Here's how we proceed.

1. Issue once the following MySQL statements (using, e.g., phpMyAdmin):
   PLAIN TEXT
   SQL:

   1. CREATE TABLE IF NOT EXISTS `tasks_problems` (
   2. `task_project` INT( 11 ) DEFAULT NULL ,
   3. `task_log_problem` TINYINT(1) DEFAULT NULL
   4. ) TYPE=MyISAM;
   5.  
   6. CREATE TABLE IF NOT EXISTS `tasks_critical` (
   7. `task_project` INT( 11 ) DEFAULT NULL ,
   8. `critical_task` INT( 11 ) DEFAULT NULL ,
   9. `project_actual_end_date` DATETIME DEFAULT NULL
   10. ) TYPE=MyISAM;
   11.  
   12. CREATE TABLE IF NOT EXISTS `tasks_sum` (
   13. `task_project` INT( 11 ) DEFAULT NULL ,
   14. `total_tasks` INT( 6 ) DEFAULT NULL ,
   15. `project_percent_complete` VARCHAR( 11 ) DEFAULT NULL,
   16. `project_duration` VARCHAR( 11 ) DEFAULT NULL
   17. ) TYPE=MyISAM;
   18.  
   19. CREATE TABLE IF NOT EXISTS `tasks_summy` (
   20. `task_project` INT(11) DEFAULT NULL,
   21. `my_tasks` varchar(10) DEFAULT NULL
   22. ) TYPE=MyISAM;
   23.  
   24. CREATE TABLE IF NOT EXISTS `tasks_users` (
   25. `task_project` INT(11) DEFAULT NULL,
   26. `user_id` INT(11) DEFAULT NULL
   27. ) TYPE=MyISAM;
   28.  
   29. CREATE TABLE IF NOT EXISTS `tasks_total` (
   30. `task_project` INT( 11 ) DEFAULT NULL ,
   31. `total_tasks` INT( 6 ) DEFAULT NULL
   32. ) TYPE=MyISAM;
   33.  
   34. CREATE TABLE IF NOT EXISTS `files_count_max` (
   35. `file_versions` INT(11) DEFAULT 0,
   36. `file_lastversion` float DEFAULT '0',
   37. `file_version_id` INT(11) DEFAULT 0,
   38. `file_project` INT(11) DEFAULT 0
   39. ) TYPE=MyISAM;

   This will create all the necessary tables.
   Note: tasks_total and files_count_max tables are 2.1.2-specific.
   Another note: for 2.1.2, the tasks_sum table is one field shorter:

   PLAIN TEXT
   SQL:

   1. CREATE TABLE IF NOT EXISTS `tasks_sum` (
   2.   `task_project` int(11) DEFAULT NULL,
   3.   `project_percent_complete` varchar(11) DEFAULT NULL,
   4.   `project_duration` varchar(11) DEFAULT NULL
   5. ) TYPE=MyISAM;

2. Now, in classes/query.class.php at line 393 (for dotProject 2.0.4; just search for the matching line in 2.1.2) replace this line:
   PLAIN TEXT
   PHP:

   1. $q = 'CREATE TEMPORARY TABLE ' . $this->_table_prefix . $this->create_table;

   with these:

   PLAIN TEXT
   PHP:

   1. //$q = 'CREATE TEMPORARY TABLE ' . $this->_table_prefix . $this->create_table;
   2. $q = 'INSERT INTO ' . $this->_table_prefix . $this->create_table;

   Now we won't get any errors about the tables which fail to be created.

3. Next, replace the following text in modules/projects/projects.class.php (lines 388-392 for 2.0.4):
   PLAIN TEXT
   PHP:

   1. // Let's delete temporary tables
   2. $q  = new DBQuery;
   3. $q->dropTemp('tasks_sum, tasks_summy, tasks_critical, tasks_problems, tasks_users');
   4. $q->exec();
   5. $q->clear();

   with this code:

   PLAIN TEXT
   PHP:

   1. // Let's delete temporary tables
   2. $sql = "TRUNCATE TABLE tasks_sum"; db_exec($sql);
   3. $sql = "TRUNCATE TABLE tasks_summy"; db_exec($sql);
   4. $sql = "TRUNCATE TABLE tasks_critical"; db_exec($sql);
   5. $sql = "TRUNCATE TABLE tasks_problems"; db_exec($sql);
   6. $sql = "TRUNCATE TABLE tasks_users"; db_exec($sql);
   7. $sql = "TRUNCATE TABLE tasks_total"; db_exec($sql);
   8. $q  = new DBQuery;

   Note: $sql = "TRUNCATE TABLE tasks_sum"; db_exec($sql); line is 2.1.2-specific.
   At this point, you will no longer receive error messages while on the "projects" tab.

4. (this point applies to 2.1.2 only) Replace lines 222 and 223 in modules/files/index_table.php
   PLAIN TEXT
   PHP:

   1. $r->dropTemp('files_count_max');
   2. $r->exec();

   with:

   PLAIN TEXT
   PHP:

   1. //$r->dropTemp('files_count_max');
   2. //$r->exec();
   3. $sql = "TRUNCATE TABLE files_count_max"; db_exec($sql);

5. Optionally, if you want to improve the performance of dotProject specifically for these tables, change the 'engine' for the above-mentioned tables to 'memory'. To do that, execute the following SQL statements:
   PLAIN TEXT
   SQL:

   1. ALTER TABLE tasks_problems engine=memory;
   2. ALTER TABLE tasks_critical engine=memory;
   3. ALTER TABLE tasks_sum engine=memory;
   4. ALTER TABLE tasks_summy engine=memory;
   5. ALTER TABLE tasks_users engine=memory;
   6. ALTER TABLE tasks_total engine=memory;
   7. ALTER TABLE files_count_max engine=memory;

   This change will make MySQL keep these tables in RAM. As they are used as temporary tables, this decreases disk I/O a lot while working with dotProject. Of course, YMMV - to apply this change or not depends on where is your bottleneck.

Comments and further improvements are welcome.

]]> http://bogdan.org.ua/2007/01/22/dotproject-204-on-godaddy-shared-hosting.html/feed 10 http://bogdan.org.ua/2006/09/27/ie-internet-explorer-margin-doubling-bug-fixes.html http://bogdan.org.ua/2006/09/27/ie-internet-explorer-margin-doubling-bug-fixes.html#comments Wed, 27 Sep 2006 13:05:23 +0000 Bogdan http://www.bogdan.org.ua/2006/09/27/ie-internet-explorer-margin-doubling-bug-fixes.html In Internet Explorer for Windows (tested with version 6 SP2), if you write CSS code similar to this:
PLAIN TEXT
CSS:
1. #floatbox
2. {
3.   float: left;
4.   width: 150px;
5.   height: 150px;
6.   margin-left: 100px;
7. }

and put your "floatbox" inside a container (such as DIV), you will actually see 200px of the left margin instead of the expected 100px. This problem is known as "IE margin-doubling bug".

In this post I collected solutions you can use to avoid this problem. The solution I'd recommend is at the end.

The first solution is to apply some minimal height to the container:

PLAIN TEXT
CSS:
1. * html .visualIEFloatFix { height: 0.01%; }

This method is described in more details here , and even better here.

Another one is to apply position:relative, this is quite an old solution, described here (there are also other fixes for the problem there, too; link returned error at the time of writing, might be a temporal problem - if not, please remind me to remove it).

Another solution is to wrap the element in another one, and apply float to that another. Removing float from the element helps avoid the trouble. This fix found here. There are lots of examples there, too.

You can also set display:inline, as described in this solution. I would recommend using this one as the most clean and compatible. To apply it to our example at the beginning, we should write the following CSS code:

PLAIN TEXT
CSS:
1. .floatbox
2. {
3.   float: left;
4.   width: 150px;
5.   height: 150px;
6.   margin-left: 100px;
7.   display: inline;
8. }
]]> http://bogdan.org.ua/2006/09/27/ie-internet-explorer-margin-doubling-bug-fixes.html/feed 2