Ok, another reason why the vb.org community will hate me… my statement, they are lazy.

since the release of the beta version, 2 weeks ago, about 60 releases were made under the 4.0 category… ALL OF THEM are just updated existing products of the 3.8 category…

no imagination
no usage of the new 4.0 engine
not even checking if their tools are still useful in the 4.0 environment…

why?… because even with the 3.8 generation, 75% of the releases made at vb.org are based on existing products, just updated or recoded… but there is no imagination in their mind or what?

that will always sustain me, to see how much power they get to code tools that nobody want… they see 1000 downloads for their tools, but how much are really useful?… people always download as much plugins as possible to install them and see how they act on their site, but are these products really efficient for their community? not sure.

i’ve seen enough of overloaded sites where people were suggested to add more and more tools, but at the end, these tools were just slowing down the usage of their site because the visitors were too occupied to learn how to navigate that they forgot to come back for the content.

i thought that the 4.0 generation would bring new ideas and new concepts from the coders… looks like i was dreaming.

I’m back at coding, after the H1N1 and some fun in the vB universe…

The subscription is at 25$, unlimited and for any version that will come.

Right now the version 1.0 is complete with the Forum side integration. version 2.0 that is on coding right now *(already, no 1.1 or 1.5 ? ) will contain the older Social Groups and other features… i just to the 2.0 version right now because it was announced sooner this year, and i have no problem to add more features and double the efficiency of the engine.

https://unpapapro.com/calendar-integration-bundle/calendar-integration-1-0-a/7200/

Right now the version is 3.8.x compatible only, and a version 4.0 will be evaluated once the vBulletin Solutions™ company release their official vBulletin 4.0 version.

I have plans to add some block for the 4.0 suite cms, but not before they end up with a final version… they move so much things in their beta that it would be cumbersome to evaluate any addon right now.

All these 4.0 things will be available only when done, there is no release date right now because i will first support the 3.8.x version.

Ok, today I started looking over the tutorials about vbulletin 4 over at vbulletin.org. As I do not have a license for it. While I was looking over the tutorials I noticed a few things.

vBulletin’s template engine is still horrible!
vBulletin STILL keeps its templates in the database. This is a HUGE performance crasher, the query to pull all the template data is going to destroy your load time. I have not seen the vBulletin templates engine code but with all the {vb whatever} commands it has to take some time to process, even if it is cached. Also having to define every variable you want to use in your PHP script is just a pain. This is why in our engine templates are PHTML files that are included. This is simple, fast, and allows complex templates just using simple < ?php brackets. vBulletin’s Class Structure is the same
vBulletin’s class structure was good, for a PHP class system 5 years ago. The $vbulletin object is massive and it gets tossed around by every function putting a huge strain on the board. My solution a static core. In my engine you call Core::whatever and every core component is available (db, templates, request cleaner, etc.), and the best part because the Core object is static it can be called everywhere without needing the global command.

Until further notice, we’re not updating our products to the newer version of vBulletin… for a single reason: we are dedicated to vBulletin’s latest official version.

vB 4.0beta is not an official version, it is not supported, and the plans are not clear on how and when they will release the Gold… so we’re not in rush to support that version here.

btw, in the next weeks i’ll be back at coding and will release all the products that were not released yet, like the Calendar and Social Groups bundles.

As I’ve I started writing the Core for our engine I’ve really started to notice we are gonna need at least a name for our engine so we can start really « integrating » it into the core. We also are going to need some sort of « branding » for it (like logo, colors, etc.), so when we start making the layout we can have a basic theme.

My idea for the name would be something that emphasizes it’s flexible or adaptable (like a synonym for one of those words).

Hey Nex,
Was just wondering if any of your mods are vB4 compatible yet?

You know what it is, when you have a flu pandemic, everybody is possibly hit by it. Your servant is not different from anyother human…

My kids were hit by the flu in the last 10 days, so i was close to no available at all lately, and now it’s me. The doctors say we need to rest for at least a week « after » the symptoms are gone… and i just start being sick, so i suppose it will be another 10 days where i risk to be offline for good.

You can still post support or requests, but be advised that you will have a sick man on the other side who just try to keep alive… rofl

see ya in a week or so!

There needs to be a better way to handle and index content. This is my idea:
– Base « content » table
— Title
— Date
— Author
— Tags
— Content
— type
— typeid (threadid, articleid, etc.)

– Thread
— All Thread options

– Article
— Article fields

( – = mysql table)
There would be a base content table with the fields above. This is the table that our search engine processes. Then every type of content « extends » this table. This way content can easily be changed (deleted from old table added to one and the id changes on the base table). This system would mean the contents actual id (the ‘content’ table’s id) would stay the same and therefor still accessible through its old URL. This also allows different types of data types to keep there special fields separate and not have a massive table with loads of data, that may only use a ⅓ of the fields.

vBulletin Beta 3 Released to Customers with 4.0 Licenses