The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
![]()
Hi, I am beginning to dive into the Product creation and was trying to find the simplest way
to manage a Product for the admin through the Install/Uninstall process. The normal process with a Product which includes files is to upload via FTP and import product.xml Is it possible to completely avoid file uploads and simply write PHP to create & delete files or will I run into folder permission problems and/or errors? Or is this possible through .xml or even a practical approach? I see some forum owners uninstall Products and such and forget to remove relevant files. Example: Import product.xml which creates any needed files (product.php,bitfields.xml,cpnav.xml,etc) And at Uninstall, all these create files would be deleted. Just curious - thanks |
#2
|
|||
|
|||
![]()
on a product, there is no file upload, you create and manage it thru the admincp only...
|
#3
|
||||
|
||||
![]()
"The normal process with a Product which includes files"
meaning a Product / Mod which has custom files in its package.(php,xml,etc) I too, have found myself uninstalling a Mod due to it becoming outdated, unsupported or just conflicting with new vbulletin or Mod updates. Then I need to figure out which files I had uploaded associated with that particular Mod. If the Mod has hit the graveyard, you can no longer download it for reference. And if you do not have a local copy for reference, it boils down to scanning the code to see how the script runs and what it calls. Mainly the reasoning behind my questions. |
![]() |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|