this is something missing from the original vBulletin. when we have a ton of products on our forum, it’s very complicated to export our styles because only one product at a time is permitted to export its templates.
with this, we can export all the templates related to a style, without checking the products.
… we have to put the $_REQUEST == ‘download’ in global.php , hook: admin_global so it work before loading the template.php file, where no hook is called….stupid!
notes:
1- with this, all templates become part of the product « vBulletin », as they can not be regrouped per product… OR we could? # i tested it, impossible.
2- we can not export multiple xml files at a time, that would have given a substancial benefit as the engine would export each template of each product in unique files, so we avoid the note #1…
…
actually i coded it late last night, around 3:00 am… so it’s not working perfect, i’ll be testing it in the evening …
Views: 39
This would be an outstanding and much needed hack, I hope the testing goes well on this, would like to see this in production 100%
it works well, i’m testing different solutions right now… 😉
solutions like size of exports and speed… 🙂
tests are good, i’ve been testing some variations, i’ll now pack the whole thing into a product.
the only downfall is that it is saving all the templates under vbulletin as the product, so if you have a lot of products, the templates may not survive the process, vBulletin have a hollowed way to deal with external products.
i’ll make a last try to generate the right template for the right product, but it requires that i recode a function that have more than 250 lines of code… 🙂
ok, i came up with the idea of rebuilding the whole process of import/export of styles from backups… and the concept is close to completion.
what it does?
1- grab the style you want to backup
2- download the entire style, only customized templates in a single xml file (default name is now backup-style.xml)
3- you can store that backup, it is complete… 🙂
4- upload the backup-style.xml AS A NEW STYLE, to avoid collision.
5- the engine will take care of each template…
—- if the product name is included, it will store the template in the proper product
—- if not, the template have to be part of vBulletin…
that’s all about it.. do i have to explain all the code changes?!.. lol there is not that many btw, i just have to copy/paste some functions and fix them to be more intelligent.
it is close to ready, but it’s late here, the release will be available by tomorrow evening for sure!
Wow! Genius!
How come this has never been done before?
hum, because it was not requested…
you know, to make a good software, you need to hear from the ones who will use it, and you also have to evaluate and think ahead of these needs… not only to create new needs, but to make them essentials.
vBulletin always been excellent in a lot of details, most of the time they were about user-end answers… my work is different, i try to answer the admin needs.
[ATTACH]113[/ATTACH]
this is a little screenshot before delivery… 🙂
as a note, there is a lot of changes between the original template import process and this one, so you can not import back a backup style to a vBulletin that does not have this product installed, because it would crap the templates database… 😉
ok, thread closed, here is the new official release: https://unpapapro.com/free-features-enhancement/backup-style/4901/