Members opinions requested…

Hi, ok, here is June coming, this is the month where i have the worst time finding ideas for new products…

So i’d like to have the members opinions and suggestions on what you’d like to see as features for vBulletin, things that do not exists or are actually working bad so you’d like a change to be made.

I can not be sure to code everything, but i’ll try… 🙂

You can post your new ideas in the Concept Box!

can you help with Classes, Drew???

here is what i get… i’m coding a « Who Quoted Me » engine, where i have to insert a new value each time someone quote a user in a post… the attached zip contain what i think may fit best…

give me your opinion please… and if you know how to grab $postid from this part of the system, tell me, because it is not called anywhere in that class, so i do not know how to grab it… 😉

the xml is the actual product, working as planned…

Progress Update..

Ok, here is just a quick status update on where i am:
– Currently I am working on making the new payment APIs as an independent product so they can be released to developers for future use. I am about a week away from finishing this (mostly just testing, probably less)
– After i finish that i am building the points engine which should be really quick because the biggest part (the payment engine) will be done. Probably 2-3 weeks
– And finally after that finishing the releases engine, which is about 75% done already, this will probably be a month to 6 weeks away.

If this time line is too slow for what you want tell me and we can figure something out:grin_Wink:

Hi, everyone

Hi, all. I’m an Australian, but living in Germany, and a long-time fan of vBulletin software, interested in coding but no good at it. Thanks for this site!

As someone else said, the smilies are definitely different! Unique, even!

Backup Style

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 product, we can export all the templates related to a backup style, without checking the products. it will create a new style with all the templates related to their proper product.

what it does for the eye:

1- a new admincp link, called « Backup a Style » in the >> AdminCP >> Styles & Templates

2- You have the choice to generate a new backup for a style OR upload an existing backup from another style.

Here are the screenshots:

nex_backup_style-backup-import.jpg

In the image above, you see the two forms that are similar to the original « Download / Upload Styles » page. The difference is that you do not have all the settings, and the file sent is different in structure.

and here is the result when you finish the import process, the new style is independant, and have a  » – IMPORT » at the end of the name if you did not edit the name as in the form above…

nex_backup_style-result.jpg

The end result is a complete independant style, with all the templates in it, no matter what products you have on your site. All the customized templates are stored in the backup file, so you have exactly the same style as the one you had first, but as a Parent style, even if you had it as a child first… because each backup is completely independant from the source, so there is no error if you forget to backup the parent style.

What is does also: you can not use the backup files on a vBulletin forum that have not this product installed… the backup will be rejected by vBulletin because the main product related to the file is missing. Also, do not try to import the backup inside the original « Download / Upload Styles » page, or it will break the stored templates… all these backups have to be used inside this engine… because it was impossible to merge both techniques inside the original vBulletin.

there is not much things to update in the future, as vB 4.0 will have a complete different engine, so the only thing that can occur by then may be bug fixes… i’m sure there will be some bugs as soon as this version 1.0.0 is released, as it’s a major code and was tested only for 2 days… so if you face bugs, instead of putting the product to the trash, please report the problem here with a screenshot or something of the bug/error… thanks!

export all templates from style X, include all templates from all products

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 …

A section for people learning to code

Hi,

Ive only just started to learn to code and must admit it is quite daunting! The actual php dosent look too bad, however its then intergrating it with vbulletin.

I was wondering if you fancied creating a section for people in the same boat as myself. Somewhere we can come to get a little bit of help and advice when stuck.

Nexia, maybe you could even take a couple of your simple mods and give a step by step approach of how you created them!

Regards

Dave