The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
![]()
im have a quite large hack that runs quite a bit of queries and adds a bunch of templates in the installation....
do you think i should use an installation php file or use an XML? |
#2
|
||||
|
||||
![]()
Use Product Management, much easier than writing custom installers.
|
#3
|
|||
|
|||
![]()
just work it into an xml product file.
It's the way to go...everyone's doing it. |
#4
|
||||
|
||||
![]()
but what if i already have a custom installer made?
THEN whats the better way? |
#5
|
||||
|
||||
![]()
Burn it and make a Product XML
![]() Shouldn't be too hard - Install using the Installer - Assign Phrases/Templates/Settings to the Product - Copy Query-Code to Product Install/Uninstall Code - Export Done. |
#6
|
||||
|
||||
![]()
and how exactly do i assign templates and stuff to the product?
oh, and will this allow me to have a php file in the admincp directory that allows me to edit the settings? |
#7
|
||||
|
||||
![]()
Go into debug mode, then create them into the Master Style, and specify the product upon creating them. You can add ACP options the same way.
|
#8
|
||||
|
||||
![]()
If you already have the phrases/templates/settings in the DB you can easily assign them by issuing a Query (UPDATE table SET product='myproduct' WHERE ...)
|
![]() |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|