True, but I will not be testing until 3.6 goes at least to RC, as there will probably be more changes through out the beta phase. Will continue to release for 3.5 until 3.6 Gold comes out and I change over to that
Kier said that no signifigant coding changes were going to to be made between 3.5.4 and 3.6 gold...so it stands to reason they could be...but it depends on the hack and wether it uses the new ACP datastore integration or involves the new features
Chief to answer your question, I will only support the version of vbulletin I myself am running. People are welcome to try the code on other versions, but I will not install test sites with that version to answer questions, etc. So, anything I release new would be for 3.6 only. If it works on 3.5, that's cool. But I'm not going to guarantee backwards compatibility.
Chief to answer your question, I will only support the version of vbulletin I myself am running. People are welcome to try the code on other versions, but I will not install test sites with that version to answer questions, etc. So, anything I release new would be for 3.6 only. If it works on 3.5, that's cool. But I'm not going to guarantee backwards compatibility.
Kier said that no signifigant coding changes were going to to be made between 3.5.4 and 3.6 gold...so it stands to reason they could be...but it depends on the hack and wether it uses the new ACP datastore integration or involves the new features
What is the new ACP datastore integration? I guess I must have missed that.
You can cache data inside of the APC so it can be pulled directly from memory instead of the database. like the filestore version.
I've never used the filestore system. I'll have to get with you on that and maybe you can show me how to use it, sir. I have a couple of small hacks for my site that use the datastore now.