![]() |
[ForumOps] vBulletin Development Environment
1 Attachment(s)
https://vborg.vbsupport.ru/
vBulletin Development Environment vBulletin Development Environment (VDE) is a tool that allows you to build vBulletin products entirely from the filesystem. By using the filesystem, it allows you to follow best practises such as using version control, and simply working on actual files. Having to switch between browser windows and copy/paste is extremely inefficient. This product has been updated to work with with vBulletin 3.5 and up to the latest 4.x series. Runtime Environment Assuming all of your files are in place, VDE checks your ./projects directory on every page load, and injects all of your projects' templates, plugins, etc. into memory and runs them as if they were natively installed into vBulletin. Product Builder VDE also comes with a project builder, which allows you to export your project into a standard product XML, and also any associated files with your project. Open Source This product is open source, and I encourage everyone who uses it to contribute back via GitHub. Installation Instructions Short version: upload files, import product XML. There are slightly different instructions based on whether or not you are running vBulletin 3 or 4. Full instructions can be found at: https://github.com/ForumOps/vBulleti...nt-Environment I will not be posting any change logs or detailed instructions here, because they may change heavily with each version. Please refer to the GitHub page. Disclaimer: this product was originally developed by SirAdrian / Adrian Schneider, who is part of our staff, and the primary maintainer of the product still. |
Awesome Adrian, thanks for releasing! - Installed!
If I weren't on staff I would nominate and vote for motm ;). |
My pleasure.
Please note, I will be posting some simple modifications built with this over the next week or two to try and provide more useful examples as there is a bit of a learning curve the first time around. |
Would anyone be interested in having the ability to generate the filesystem stuff based on the product data in vBulletin? (reverse the build process)
Usage would be something like, Code:
php vde.php import product_id |
yes! copying phrases from the admin into seperate text files is a big PAIN!
|
Awesome stuff :)
I thought about building smth. similar for a long time but never had enough time / interest to actually start developing. You could avoid the file edit by changing PHP Code:
PHP Code:
|
Nice, I'll try this out on my next vB project. :up:
|
interesting mod, will try it soon in the summer holiday :D
|
Thanks, Andreas. :up: I'll try to get that updated soon, as I hate file edits.
|
Quote:
|
I actually needed the ability to port an existing product into VDE today so it has been written! I'll update Github first within the next few days (maybe sooner) and the actual packages a bit later as time permits.
|
Update: you can now specify entire directories by name rather than having to list each of their files in a project's config.php file.
Example, Code:
array('files' => array( Code:
array('files' => array( Also, you can now import existing products into VDE automatically, by using the 'port' command: Code:
php vde.php port existing_product_id projects/save_here Has anyone had a chance to build a plugin from scratch with this yet? Would love some feedback, especially on the documentation side of things as it was quite rushed. I've been using this method for years, so my steps are probably lacking. |
Quote:
And Adrian coming along even better I should have been eying this closer per your comments on messenger... I believe Adrian said it took them 3 hours to port a product that should have normally taken 30+ hours via the admincp (huge btw) so all-in-all this is killer imo! I still have not tested this myself however I have installed it on the forum some of us Advisors here use as I thought it might be helpful to BirdofPrey5 and DigitalJedi if they wanted to utilize it and well me too eventually. Just plain awesome :cool:. |
Great work Adrian,, Thank you!
|
Not working with me!
Warning: scandir([path]/projects) [function.scandir]: failed to open dir: No error in [path]\includes\vde\runtime.php on line 115 Warning: scandir() [function.scandir]: (errno 0): No error in [path]\includes\vde\runtime.php on line 115 Warning: Invalid argument supplied for foreach() in [path]\includes\vde\runtime.php on line |
Quote:
https://github.com/ForumOps/vBulleti...nt-Environment |
Quote:
Cheers |
Getting an error when trying to port an existing mod..
From the style of the command, I would assume this needs to be run from a terminal window. Code:
php vde.php port advapp projects/advapp |
The download package here is old... I will be updating it today. We've made few updates since it was released.
If you download the latest version from GitHub it should solve your problems. Cheers |
Thanks, that worked.
But, I must be missing something really simple.... With the development environment enabled, my mod stops working completely. Disable the development environment and it works fine. |
Nevermind, I had to enable it in the project directory.
|
I'll push a proper update out tomorrow with the latest code, a fix for that file edit, and a few more updates to the documentation (FAQs, perhaps)...
Glad to hear you figured it out. |
Sorry guys, still having to update.
How many of would find this useful for style development? (if it's possible) |
Are there screens?
|
There are absolutely no interfaces anywhere, so there is nothing to screenshot. :)
|
Adrian, just a heads up, the link in your forumops signature has an invalid thread id
also, do you think it would be possible to load options into the vbulletin admincp runtime to make sure i have textfields yesno etc set properly? |
Hmmm, it works for me (as guest or as member). Can you PM me the details so I can look into it?
To answer your question... no, unfortunately. That would be a ton of work and would probably have duplicate some vBulletin code. I guess you get used to the different development style, and when something is somewhat stable, you can export it to another test site to test. You technically can export, disable VDE, and import on the same site, but it can get a little confusing so I like to keep it separate. I'll think about what the options are... maybe there is an easy way. |
no biggie :) will pm you about the broken link.
|
Fantastic effort Adrian,
I for a long time have wanted to get into this type of thing and so this will definately be a start. I am pretty sure it is my thing that you said would normally take 30+ hours but using this was done in the space of about 3 hours. I have voted for motm for you. |
also, im having a problem with this since the newest update. has anything changed with the options? i see my options files being included on the page.
I have a usergroup id number set in the options, and im an additional user in that usergroup id, however PHP Code:
PHP Code:
|
yes, i dont seem to be getting the use of $vboptions or $vbulletin->options for products with VDE
filename: vbay_seller_usergroups.php PHP Code:
|
ah, yes.
PHP Code:
@Brendon, there were two projects I did around the same time, but yours was one of them, yes. :) Yours was the first of the two, so it was a little slower, but the second one was super quick. And guys, I'm guilty. I still have to push some updates and update the packages as well. |
oh good! i was thinking i was just having a derp moment and missing a semicolon or bracket somewhere ;)
edit: and yes that fixed it for me. thanks muchly. |
Would you guys be interested in some sort of mechanism to allow you to have all of your files + projects directory OUT of vBulletin, for the sake of easier (and lighter) versioning?
Phase 1 would be support for the projects to live outside of vBulletin. Have a command line function to copy all of the files into vBulletin. (or for power users, rsync or similar to keep the directories in sync) Phase 2 would be a PHP-based solution for this, though I'm not really sure what that would look like yet in terms of linux + windows compatibility... Any thoughts? |
Jesus christ, what a mod! Adrian, we germans call that the eierlegende Wollmilchsau (a funnier version of one-does-it-all)! Great work, much appreciated. Nominated.
|
Glad you like it. :D
It has been an enormous help to me on a daily (hourly?) basis. |
Adrian, I am somewhat a noob at coding and at developing software, would this be a good place to start with? Would it be easy for me to start developing my own mod with this tool? I have owned and managed my website for over 2 years and do all of the "technical" stuff but haven't really put myself to learn the actual development; in the last weeks I have dived in , literally dived in to a warm delicious pool of codes and variables and I must say I LOVE IT! Any pointers for a noob to start playing with this mod to get a better handle on how vb modification come about? Or any light in the right direction for that matter would be awesome. Thanks Adrian! :)
P.S.: Anyone looking to be a mentor for a "natural" (wishful thinking) coder please let me know. :) P.S.: Joined Github - EquinoxAW |
VDE adds a small layer of complexity on top of what exists already, so I can't say whether or not it will help you understand programming.
However, if you use it to convert a downloaded product into actual files you can look at it, you will be able to get your hands dirtier a lot faster since you can edit a file, save it, and see what happens. Best advise I can give you is to ask a ton of questions. The private coders discussion forum is probably your best bet for vBulletin stuff. Cheers |
Next planned features:
Include other files in a release - Immediately - Add a way to include other files as part of the release that don't go in 'upload'. This will probably be a new subfolder per project so you can create folders such as "do_not_upload" or "docs" in there. Merging Automatic Template Compiler with VDE - Several Weeks - ATC is a similar modification to VDE, but instead of running things from filesystem and injecting into memory, it actually persists the templates properly into a style. This is fantastic for style development, or if you are working on an actual site and not just a product you want to distribute. I'm working on a large new forum / skin / etc. right now, and I've created a original_templates and customized_templates inside of my project folder. If I want to customize a stock vBulletin template, then I copy it from original into customized, and as soon as I edit it, it will actually edit the template inside vBulletin. This allows us to still export the style as we normally would. I plan on doing something similar for stock phrases, stylevars, etc. since when working on an actual site, it is crucial to modify this stuff. Who here would find this useful? If not, I'll keep doing it how I'm doing it and not further develop it. |
Quote:
|
All times are GMT. The time now is 04:50 AM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|