vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 3 Articles (https://vborg.vbsupport.ru/forumdisplay.php?f=187)
-   -   [How-To] Product Managament (vBulletin 3.5 RC 1 and up) (https://vborg.vbsupport.ru/showthread.php?t=92953)

Paul M 07-29-2005 04:49 AM

Now all we need is the ability for this to upload new files (extensions) edit templates & edit files. Then it will be a complete installation system.

Andreas 07-29-2005 08:17 AM

Quote:

Originally Posted by MrNase
Custom vBulletin settings must be added with a query? Or is there a function available with adds them without using a query?

Assign them to your Product, then Product Management will take care of Installing/Uninstalling :)

Andreas 07-29-2005 08:18 AM

Quote:

Originally Posted by Paul M
Now all we need is the ability for this to upload new files (extensions) edit templates & edit files. Then it will be a complete installation system.

I for one wouldn't like that. Especially editing Templates can be tricky, as you never know for sure how they will loke like.

Logikos 07-29-2005 08:46 AM

Quote:

Originally Posted by KirbyDE
I for one wouldn't like that. Especially editing Templates can be tricky, as you never know for sure how they will loke like.

Editing templates should be the users task only. Due to style customizations. But uploading files from the admincp would complete this! :)

MrNase 07-29-2005 10:39 AM

Quote:

Originally Posted by KirbyDE
Assign them to your Product, then Product Management will take care of Installing/Uninstalling :)

That must be done in the debug mode? Because all other things can be done without it..

Andreas 07-29-2005 10:50 AM

Templates, Phrases, Settings and Plugins must be created in Debug Mode - as stated in the first Post.

Erwin 07-29-2005 11:44 AM

Quote:

Originally Posted by Paul M
Now all we need is the ability for this to upload new files (extensions) edit templates & edit files. Then it will be a complete installation system.

I agree. And add a file editor to that, and you have everything. ;) Better yet, have ALL of the code in XML format. No more file edits... ever.

Andreas 07-29-2005 11:46 AM

I have to disagree. File and especially Template Edits should stay a User task, as they can be quite complicated keeping customized Styles and different Versions in mind.

deathemperor 07-29-2005 04:07 PM

Thanks Kirby, you should write books for vbulletin.

Dream 08-01-2005 11:43 AM

can I use version numbers like 1.0 or 1.9.5


All times are GMT. The time now is 11:10 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2024, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.02240 seconds
  • Memory Usage 1,730KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (5)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete