5
Quote:
irmtfan wrote:
Quote:
I wrongly thought so. but after installing 2.6.0 alpha 1 i saw that they are common modules and nothing more.
Please see the code of new modules. it will take just 5 minutes for you.
I wish the extensions will be something you describe them in the 2.6.0 final version.
As I said, I believe they are moving in that direction.. Separating them into modules is a great first step. Not sure how this will impact modules using things like the ratings system though...
Quote:
about MySQL:
Quote:
has been rumored to be truly depreciated as of PHP 5.4 and rumored to be removed as of PHP 5.5.
it is really dangerous for us. once we can be sure about it we should do some immediate actions. therefore i think we should move ASAP to other connectors.
I converted the current MySQL connector to the newer MySQLi connector and tested it with an older 2.5.x variant for about 10 minutes and It worked fine for me. This could be further debugged and used if necessary. It MAY work as is but like I said, I have not tested it with other modules I just tested it with the core and it ran fine.
See here for details:
https://xoops.org/modules/newbb/viewtopic.php?post_id=347185#forumpost347185Quote:
about ADODB:
Quote:
This code is unsupported at this time and written in PHP for both versions.
.....
This is not a normally installed library and needs to be installed by the user. Speed increases for this connector require not only changes to the core code to take advantage of the new features but also requires a PHP compiler or something similar to speed up the PHP code.
very bad. we should leave it.
Yes and if you look at the code that Wishcraft has made available in the SVN it is hard to follow because he jumps around and can be rather cryptic.
http://xoops.svn.sourceforge.net/viewvc/xoops/ThirdParty/adodb/When the PDO topic is brought up I think Simon gets confused and brings up the adodb stuff but this would need lots of work to make it worthy of putting into the core if it even works.
Oh and again, we do NOT want ADODB.. It will be SIGNIFICANTLY slower than the current MySQL or MySQLi connector when not used with a PHP accelerator of some type. It is very confusing from the files here what Simon is actually using. I offer the link here so you can see for yourself.
Quote:
about PDO:
Quote:
This is very similar to ADODB but has no connection to Microsoft's database connection system.
this is very good!
Also IMO core team must move from MyISAM and add Innodb.
I saw mention that the databases were getting converted to Innodb but my research shows that ONLY when you are using the new features of MySQL 4.x+ is this a good thing. If you are using a simple database that doesn't need transactions or possibly some types of external (Foreign) keys MyISAM is still substantially faster.
Quote:
Quote:
we can expect MOST modules to work with 2.6 if they work with 2.5.5 but they will need to be upgraded totally to work before 2.7 and there will be "depreciated" warnings given when in debug mode.
From what i see in codes the above is not done correctly.
I can see many errors in installing some new modules that worked fine in 2.5.5
Core team should correct them. Also some members like me and you should test more and report.
I gave the link to what Trabis said but Trabis has not been involved for a while due to other obligations. I believe that it should not be a big deal to provide code with depreciation warnings but I am not a core developer. But for this and other reasons when Module developers develop new modules they SHOULD separate xoops related code into their own classes to make converting to newer versions simpler but that is on the Module Developer. At this time there is very little useable Module Developer Documentation that is up to date. This is a huge problem and one Mamba has been trying to get done for a long time but he needs a module developer to spend the time to develop the resource.
Quote:
Quote:
The solution here is to make sure only Xoops API code is used.
we should promote that more.
I cannot see any module that use only Xoops API. module developers dont know Xoops API completely and Xoops API in 2.5.5 is rather more complex than 2.6.0 with some parallel methods (eg: global variables and classes and functions.)
I hope in 2.6.0 all module developers just use Xoops API to connect to database.
Also core team deprecated all useful functions like formatTimeStamp and promote to use XoopsLocal::formatTimeStamp instead which i still dont know the reason.
could you tell me that great reason?
I have more to say but now i have not time.
I can't speak for the developers here but I believe moving to the all inclusive $xoops class is to simplify things and help get away from extensive global variable use. The more use of global variables the less secure it becomes.
Also, another item that should be mentioned about PDO is that it is SIGNIFICANTLY more secure than the MySQL and MySQLi connectors. I don't know about the ADODB connector in this respect but the security aspect is secondary only to the choice of databases in importance for moving to PDO.
Again, even if 2.6 does break 100% of modules as I expect it does right now at the alpha 1 stage, it is NOT a big deal to convert modules over based on Trabis's comments. But if we don't have transitional code to make it work while showing "depreciated" it will surely need to be well documented and pointed out in numerous places.
Attending College working towards Bachelors in Software Engineering and Network Security.
