Re: [Slashcode-general] my 2x -> 2y upgrade

[Adam K. <as...@en...>]

> In INSTALL, there is a significant amount of text devoted to telling you
> how to see which templates have changed, and how to get the new templates.

I read it. I didn't fully understand it. But went ahead anyway. And was
pleasantly surprised that the site was still there afterwards. Presumably,
this means that I'm using old templates -- including admin ones, when I
should be using the new ones. It's not clear to me where the new templates
are. With the template-* tools I suppose it's not necessary to know that,
but:

> do template-tool -u VIRTUAL_USER -s *)

I just did that in the /usr/local/slash/plugins/Admin directory and got
this:

--------

Preparing to insert  using filename PLUGIN
created template PLUGIN tpid 151
Preparing to insert  using filename admin.pl
DBD::mysql::db do failed: Duplicate entry 'misc-default-en_US' for key 2 at
/usr/local/lib/perl5/site_perl/5.6.0/i586-linux/Slash/DB/Utility.pm line
347, <FILE> line 1350.
Error in
library:Slash::DB::Utility:/usr/local/lib/perl5/site_perl/5.6.0/i586-linux/S
lash/DB/Utility.pm:332:INSERT INTO templates () VALUES()

Which was called
by:Slash::DB::MySQL:/usr/local/lib/perl5/site_perl/5.6.0/i586-linux/Slash/DB
/MySQL.pm:3088:INSERT INTO templates () VALUES()

created template admin.pl tpid 152
Preparing to insert  using filename dump
DBD::mysql::db do failed: Duplicate entry 'misc-default-en_US' for key 2 at
/usr/local/lib/perl5/site_perl/5.6.0/i586-linux/Slash/DB/Utility.pm line
347, <FILE> line 1366.
Error in
library:Slash::DB::Utility:/usr/local/lib/perl5/site_perl/5.6.0/i586-linux/S
lash/DB/Utility.pm:332:INSERT INTO templates () VALUES()

Which was called
by:Slash::DB::MySQL:/usr/local/lib/perl5/site_perl/5.6.0/i586-linux/Slash/DB
/MySQL.pm:3088:INSERT INTO templates () VALUES()

created template dump tpid 152

-----------

> you need to update existing templates that have changed, as
> per the upgrade instructions in INSTALL.  That is, you need to dump your
> templates with template-tool, compare them against the new ones with
> template-check, and then (either by modifying the dumped template and then
> saving it back, or editing the template in the web interface, or just
> saving back the new template) get the changes into the database.

Er, I don't really know what I'm doing with this tool. I see HTML but I
don't know what it belongs to and then I get a long list of "grep: writing
output: Broken pipe" notices. Until I've got a bit more time to figure it
out, can I just transfer the new admin stuff to the place where the old
admin stuff is currently being read from? Where is the new stuff and where
should it be to be activated?

Feeling dense,

AsK