next »

[V-man]

A number of issues have been traced to the use of MySQLi databases. These include the inability to see events, modify the JCal settings, and installation errors.

If you experience any of these, please revert to a standard MySQL database before posting in the forum.

[mrossini]

It's *really* IMPOSSIBLE to run JCal Pro 1.5.3 with MySQLi ?

 
Matteo

[V-man]

I don't know if it's impossible, but we are not supporting it. That said, if you figure it out, please post it here.

[sundog_ak]

Here is a modification that will allow use of the mysqli function in Joomla. I have a SMF bridge that requires the use of MySQLi calls, so I poked around for a fix since the option of just not using MySQLi wasn't available in my case.

I cannot say that I figured out the fixes. There is a very useful tool at MySQL that will convert a php file from mysql calls to mysqli for you.  You can read more about that tool here:
http://forge.mysql.com/wiki/Converting_to_MySQLi

You can download the tool here:
http://dev.mysql.com/get/Downloads/Contrib/mysqli_converter/mysqli_converter-1.0.zip/from/pick

The key file for JCal Pro that is having issues is the dblib.php file.  It is located here:

Code:

public_html/your_joomla_folder/components/com_jcalpro/include/dblib.php

I ran the conversion tool on this file. There may be other database calls in other php files, but this was the one that was giving me errors in my website log so I tried it first.

I have attached the modified php file to this email.  Rename the attached file to "dblib.php" and replace the original file in the above directory. If you are nervous about using the file as is, you can download the conversion tool and convert your file directly.  See the above links on how that tool functions/commands/installs.

A quick comparison with Notepad++ (using compare function) of the two files (original and modified) indicates that about 10 lines were changed by the tool, mostly calls from mysql changed to mysqli, however, there were also other command changes so I cannot say the fix is simply to search and destroy a simple search string. 

Obviously, if there are updates to JCal Pro in the future, then this file will probably have to be reconverted unless future development includes mysqli calls in the future. 

Caveats:

Use at your own risk. I haven't tested this fix extensively yet but it appears to fix the blank page issues that I was having.

I had already installed JCal Pro, so I do not know if there are still problems with installation. 

Cheers,
Chris

[V-man]

R-iterate: use at your own risk.

Also, smf does not require MySQLi.

[sundog_ak]

SMF doesn't, but the bridge I am using does require MySQLi:

http://www.gmitc.biz/products/j2smf.html

[pashmak]

Has anyone fixed this problem???

[olafos]

I'm using a mysqli database - and want to use JCalPro for Joomla 1.5.

V-man wrote:
If you experience any of these, please revert to a standard MySQL database before posting in the forum.

My question:
How do I revert from mysqli to mysql on a live site?

[V-man]

This question is best sent to your hosting provider. It will vary system to system.

[mx5gr2]

Under MySQL (let alone MySQLi), when either the minical or the events_latest modules are used, the website cannont open at all (frontend), it times out. With the modules disabled, it opens up fine.

Any suggestions? Better MySQL indexing perhaps?

[olafos]

From global configuration - server - database settings: Change the setting from mysqli to mysql.
I did this myself - and it worked fine!
Good luck (backup database first? - just to be safe).

[mx5gr2]

From global configuration - server - database settings: Change the setting from mysqli to mysql.
I did this myself - and it worked fine!
Good luck (backup database first? - just to be safe).

Already did that and we are operating under mysql (not mysqli). When the modules are used, however, the site times out (and the PHP execution limit is 500 secs)

[olafos]

I would have tried to uninstall all JCal modules and components, then install again.

[mx5gr2]

I would have tried to uninstall all JCal modules and components, then install again.

Done that as a first step towards a solution...to no effect