B
benjiprince
Guest
Here is some helpful information from Plesk support regarding updating the the non appearance of the templates in sitebuilder root admin templates list after installing some of the RPM files
If you want to install new templates from RPM, you should follow these steps:
1. install template pack: rpm -ivh xxxx_xxx-1.0-0.i386.rpm
2. enter to /usr/local/sitebuilder/repository/templates directory
3. run this command: ls > tmpl_inst
4. Login to Sitebuilder as admin. Enter to Templates section.
After that you should divide new templates into categories.
I sorted my categories out through phpmyadmin by noting down all category names from sitebuilder root admin panel (ie. as they are listed in alphabetical order you find:
Art and Photography
Beauty
Business
Cafe and Restaurant
etc ... etc ....
so it follows that in the templates database table:
category_id 1 belongs to Art and Photography
category_id 2 belongs to Beauty
category_id 3 belongs to Business
category_id 4 belongs to Cafe and Restaurant
All the newly installed sitebuilder2 templates seem to be given the default category_id of:
category_id -1
If like me you have the access to phpmyadmin or other mysql knowledge then this is how i did the job to easily assign my templates in Category name order
I entered mysql phpmyadmin as mentioned above and searched for the template categories that I want to re-asign a new category_id number to:
that is; to say, I searched for Business in category name field
This brings into my list all the business templates showing each one to have the default category_id of -1
I changed the category_id for all in this business list from -1 to 2 as they were seen in the alphabetical numbered order in the sitebuilder root admin category list section. (see above previous example list)
I did the same search and replace method for each template category and its corresponding category_id as they fell in list order.
Obviously, I backed up all relevant files prior to doing any alterations in case the above trial method was unsuccessful.
For me it worked speedily
If you follow my examples then you do so at your own risk.
I hope the information is helpful.
If you want to install new templates from RPM, you should follow these steps:
1. install template pack: rpm -ivh xxxx_xxx-1.0-0.i386.rpm
2. enter to /usr/local/sitebuilder/repository/templates directory
3. run this command: ls > tmpl_inst
4. Login to Sitebuilder as admin. Enter to Templates section.
After that you should divide new templates into categories.
I sorted my categories out through phpmyadmin by noting down all category names from sitebuilder root admin panel (ie. as they are listed in alphabetical order you find:
Art and Photography
Beauty
Business
Cafe and Restaurant
etc ... etc ....
so it follows that in the templates database table:
category_id 1 belongs to Art and Photography
category_id 2 belongs to Beauty
category_id 3 belongs to Business
category_id 4 belongs to Cafe and Restaurant
All the newly installed sitebuilder2 templates seem to be given the default category_id of:
category_id -1
If like me you have the access to phpmyadmin or other mysql knowledge then this is how i did the job to easily assign my templates in Category name order
I entered mysql phpmyadmin as mentioned above and searched for the template categories that I want to re-asign a new category_id number to:
that is; to say, I searched for Business in category name field
This brings into my list all the business templates showing each one to have the default category_id of -1
I changed the category_id for all in this business list from -1 to 2 as they were seen in the alphabetical numbered order in the sitebuilder root admin category list section. (see above previous example list)
I did the same search and replace method for each template category and its corresponding category_id as they fell in list order.
Obviously, I backed up all relevant files prior to doing any alterations in case the above trial method was unsuccessful.
For me it worked speedily
If you follow my examples then you do so at your own risk.
I hope the information is helpful.