Sidebars and plugins gone

[rj]

I just moved Serendipity from one host to another. I upgraded to 1.3 also. Got it installed and the DB is working!

Two problems I bet are related and simply something I forgot to do.

The sidebars are gone even though they are in the style.css. And what I am sure is related...

Config Plugins is empty, total ZERO for both Events and Sidebar. When I click to install one, it downloads to the admin screen, I SAVE, it says saved, but the plug in is not added, it is still at total zero no matter Events or Sidebar.

http://rackjite.com

thanx

RJ

[garvinhicking]

Hi!

Please read the FAQ on how to move an installation: you most surely have forgotten to fix the paths in your serendipity_plugins DB table.

Regards,
Garvin

[rj]

Thanx, it led me to the problem!

The server (GoDaddy) stopped importing the DB before it got to the "P" tables! The DB import is incomplete. On numerous tries I might add.

Been through this with them before, they say I have to break the DB up into small pieces to import. I have no idea how to do that.

It is rackjite.sql. It is 6.4 megs. They say break it into 3 equal parts and it will import.

Any ideas how or where to break it up? How does that work?

Thanx

RJ

[garvinhicking]

Hi!

Maybe you can export every single tables as one .sql file, then you can import those small pieces again.

Other than that, you'd have to use a texteditor and split up the file; cut it just before a "CREATE TABLE" statement.

Regards,
Garvin

[rj]

I have tried numerous things... Splitting it up by hand, using a 3rd party DB dumb php, and trying the new server RESTORE front end at Godaddy.
But it always stops, or errors out, at this table for this reason:

----------------------
Error

SQL query:

CREATE TABLE `serendipity_permalinks` (
`permalink` varchar( 255 ) NOT NULL default '',
`entry_id` int( 10 ) unsigned NOT NULL default '0',
`type` varchar( 200 ) NOT NULL default '',
`data` text,
KEY `pl_idx` ( `permalink` ) ,
KEY `ple_idx` ( `entry_id` ) ,
KEY `plt_idx` ( `type` ) ,
KEY `plcomb_idx` ( `permalink` , `type` )
) TYPE = MYISAM ;

MySQL said: Documentation
#1071 - Specified key was too long; max key length is 1000 bytes
------------------

I dont know what a KEY is.
Its a rather big table too... Under a meg though...

The entries table is the big one at 4.4 megs (1500 articles)
Total DB is 6.4 megs

[garvinhicking]

Hi!

Seems you created a database with a different collation than your old one. Try to switch from UTF-8 to latin1 / latin1_general or something like it, through the phpmyadmin interface.

The key length error happens when the server reservers more characters for UTF-8 strings than are required otherwise.

You could also modify the SQL to this:

Code: Select all

CREATE TABLE `serendipity_permalinks` (
`permalink` varchar( 255 ) NOT NULL default '',
`entry_id` int( 10 ) unsigned NOT NULL default '0',
`type` varchar( 200 ) NOT NULL default '',
`data` text,
KEY `pl_idx` ( `permalink` ) ,
KEY `ple_idx` ( `entry_id` ) ,
KEY `plt_idx` ( `type` ) ,
KEY `plcomb_idx` ( `permalink`(155) , `type`(64) )
) TYPE = MYISAM ;

HTH,
Garvin

[rj]

This problem is really about Godaddy and that damn 2 meg upload limit. Damn them all to hell!

I am now using a 3rd party PHP program called BIGDUMP.PHP. It breakes tables up for uploading. When I changed to the permalink table code you gave me, it made it past there and a couple more tables, and then did the same stall error here...

-------------
Error at the line 1158: ) TYPE=MyISAM;

Query: CREATE TABLE `serendipity_plugincategories` (
`class_name` varchar(250) default NULL,
`category` varchar(250) default NULL,
KEY `plugincat_idx` (`class_name`,`category`)
) TYPE=MyISAM;

MySQL: Specified key was too long; max key length is 1000 bytes
-----------

I tried doing a few things with both latin1 and utf8 and that seems not to make any difference... Though not absolutely sure.

[garvinhicking]

Hi!

Have you used that method I mentioned to specify key length inside the CREATE TABLE statement? Look at the code snippet I made.

I tried doing a few things with both latin1 and utf8 and that seems not to make any difference... Though not absolutely sure.

What exactly did you try?

Regards,
Garvin

[rj]

I imported the DB file as both latin1 and utf8 and both seemed to work the same. I am now just sticking with utf8 because it worked with the snippet you gave me.

The snippet you gave me for the PERMALILNKS table did get me past the error in that table but I got the same error in the plugincategories table down a bit further.

I do not know how to apply the snippet to the plugincategories table as it is structured differently... I do not understand the snippet, or how these tables work, I am just doing what a monkey does.

-------------
Error at the line 1158: ) TYPE=MyISAM;

Query: CREATE TABLE `serendipity_plugincategories` (
`class_name` varchar(250) default NULL,
`category` varchar(250) default NULL,
KEY `plugincat_idx` (`class_name`,`category`)
) TYPE=MyISAM;

MySQL: Specified key was too long; max key length is 1000 bytes
-----------

PART 2

A few days ago, even with the partial DB up, the blog presented and functioned somewhat, something I did changed that and now all it presents is this
---------
Warning: Smarty error: unable to read resource: "404.tpl" in /home/content/r/a/c/rackjite2/html/webkick/bundled-libs/Smarty/libs/Smarty.class.php on line 1092
--------------

Whats that about ya think?

[garvinhicking]

Hi!

I imported the DB file as both latin1 and utf8 and both seemed to work the same. I am now just sticking with utf8 because it worked with the snippet you gave me.

Ah, the uploading would not make a difference. But the charset WITHIN the .sql file would need to be changed, respectively the charset you chose when exporting the dump.

Use this:

Code: Select all

CREATE TABLE `serendipity_plugincategories` (
`class_name` varchar(250) default NULL,
`category` varchar(250) default NULL,
KEY `plugincat_idx` (`class_name`(127),`category` (127))
) TYPE=MyISAM;

The trick is to simply add numbers after the fieldnames within the KEY section and make sure that all keys do not add up to more than 255 characters. On latin1, the limit is 500 characters.

A few days ago, even with the partial DB up, the blog presented and functioned somewhat, something I did changed that and now all it presents is this
---------
Warning: Smarty error: unable to read resource: "404.tpl" in /home/content/r/a/c/rackjite2/html/webkick/bundled-libs/Smarty/libs/Smarty.class.php on line 1092
--------------

That can happen if either files are missing or the path you entered in the configuration is not valid/does not exist.

Regards,
Garvin

[rj]

DATABASE IMPORT SUCCESSFUL!!!!!


And it seems I got the PATH right. The issue is that I am running numerous domains off the same host and the REAL directories are different than the domain directory... Or something like that

Its a mess but its functioning and seems to be all there!

So thanx a big bunch Garvin... I was at my wits end there.

Got a big mess to fix but its doable now!

Thanx

RJ

[rj]

Thanx again for the help, I was really really stuck.

It all works now except the categories.

When I click on them I get NO ENTRIES TO PRINT.

The entrycat table seems to be there okay...

When I go to the categories screen in ADMIN they are all listed but when I click to edit one, the name and description are missing and have a > character instead of a name.

http://rackjite.com/

thanx

RJ

this is my .htaccess file just in case

---------------
Options +FollowSymLinks
Options +Includes
AddHandler server-parsed .htm

#www rewrite
RewriteEngine on
RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} !^rackjite\.com
RewriteRule (.*) http://rackjite.com/$1 [R=301,L]

# BEGIN s9y
ErrorDocument 404 /index.php
DirectoryIndex /index.php

RewriteEngine On
RewriteBase /
RewriteRule ^((archives/([0-9]+)-[0-9a-z\.\_!;,\+\-\%]+\.html)/?) index.php?/$1 [NC,L,QSA]
RewriteRule ^(authors/([0-9]+)-[0-9a-z\.\_!;,\+\-\%]+) index.php?/$1 [NC,L,QSA]
RewriteRule ^(feeds/categories/([0-9;]+)-[0-9a-z\.\_!;,\+\-\%]+\.rss) index.php?/$1 [NC,L,QSA]
RewriteRule ^(feeds/authors/([0-9]+)-[0-9a-z\.\_!;,\+\-\%]+\.rss) index.php?/$1 [NC,L,QSA]
RewriteRule ^(categories/([0-9;]+)-[0-9a-z\.\_!;,\+\-\%]+) index.php?/$1 [NC,L,QSA]
RewriteRule ^archives([/A-Za-z0-9]+)\.html index.php?url=/archives/$1.html [NC,L,QSA]
RewriteRule ^([0-9]+)[_\-][0-9a-z_\-]*\.html index.php?url=$1-article.html [L,NC,QSA]
RewriteRule ^feeds/(.*) index.php?url=/feeds/$1 [L,QSA]
RewriteRule ^unsubscribe/(.*)/([0-9]+) index.php?url=/unsubscribe/$1/$2 [L,QSA]
RewriteRule ^approve/(.*)/(.*)/([0-9]+) index.php?url=approve/$1/$2/$3 [L,QSA]
RewriteRule ^delete/(.*)/(.*)/([0-9]+) index.php?url=delete/$1/$2/$3 [L,QSA]
RewriteRule ^(admin|entries)(/.+)? index.php?url=admin/ [L,QSA]
RewriteRule ^archive/? index.php?url=/archive [L,QSA]
RewriteRule ^(index|atom[0-9]*|rss|b2rss|b2rdf).(rss|rdf|rss2|xml) rss.php?file=$1&ext=$2
RewriteRule ^(plugin|plugin)/(.*) index.php?url=$1/$2 [L,QSA]
RewriteRule ^search/(.*) index.php?url=/search/$1 [L,QSA]
RewriteRule ^comments/(.*) index.php?url=/comments/$1 [L,QSA]
RewriteRule ^(serendipity\.css|serendipity_admin\.css) index.php?url=/$1 [L,QSA]
RewriteRule ^index\.(html?|php.+) index.php?url=index.html [L,QSA]
RewriteRule ^htmlarea/(.*) htmlarea/$1 [L,QSA]
RewriteRule (.*\.html?) index.php?url=/$1 [L,QSA]

<Files *.tpl.php>
deny from all
</Files>

<Files *.tpl>
deny from all
</Files>

<Files *.sql>
deny from all
</Files>

<Files *.inc.php>
deny from all
</Files>

<Files *.db>
deny from all
</Files>

# END s9y

[garvinhicking]

Hi!

Did you maybe use a Database import from a s9y version different than your current version? Like if you used 1.2 on the old host, and 1.3 on the new one?

In that case, you missed the DB upgrade. Please check out the FAQ on how to re-perform it.

When you migrate, always make sure you migrate to the SAME VERSIOn installed previously. You cannot migrate+update in one go.

Regards,
Garvin

[rj]

Oh no! Thats what I did!
I installed the upgraded 1.3 onto the new host, and then moved the 1.2 DB.

I am unclear on what to do after reading the FAQ.
Upgrade it all again with the old DB in there?

Thanx

RJ

[garvinhicking]

Hi!

I am unclear on what to do after reading the FAQ.
Upgrade it all again with the old DB in there?

Please follow the steps that are outlined detailed here:

http://www.s9y.org/11.html#A20

Those steps 1, 2 and 3 you need to execute. You might not need step 1 if you can already write to serendipity_config_local.inc.php.

Your "versionInstalled" string will then be "1.2".

Regards,
Garvin