| Re: Database problem |
| by Timelord1957 on 2010/8/7 15:47:54 Yes. I discovered the "ENGINE=" later in the day when trying Joomla (which has the same problem). In all actuality, unless there is a specific reason to USE the MYISAM engine, it would be JUST as easy to leave the TYPE=/ENGINE= option out. I installed fine without either of these. FYI, I STILL prefer XOOPS to Joomla, Drupal and DotNetNuke (the latter mainly because it seems to be limited to Microsoft platforms). |
| Re: Database problem |
| by ghia on 2010/8/6 21:52:13 Timelord1957, Welcome to the XOOPS forum! Thank you for reporting this! The TYPE=MyISAM is deprecated in the latest MySQL versions and has to be replaced by ENGINE=MyISAM I guess this would also work on your system. An entry has already been made in our bug tracker on SourceForge. |
| Re: Database problem - Re: Unable to create table |
| by Timelord1957 on 2010/8/6 19:43:28 There IS ONE OTHER "BUG" in the Database installation part of XOOPS that I discovered that DEFINITELY prevents the installation and it has NOTHING to do with Permissions - Database or OTHERWISE! The creators of the SQL scripts add the table type (TYPE=MYISAM) to the end of each table creation line. Some sites (like my home system) are not set up to select a storage type. MY MySQL server, for example is explicitly INNODB. It is the current stable release of MySQL, by the way. Since the servers are mine, I was able to discover the error by locating the script in question, adding a connect line (ie. CONNECT MYDATABASE) at the beginning and executing it from the Unix Shell (BASH in My case) as: # cd /rootlocation/install/sql # vi mysql.structure.sql (insert the correct connect line and save) mysql -u mjmgr -p <mysql.structure.sql And you get the error that TYPE=MYISAM is not a valid SQL command for this MySQL installation. The fix? Re-Edit the file, removing the connect command and go to each table creation line and REMOVE the TYPE=MYISAM option. (You can use SED or other methods if you are confident enough.) The installation process then works GREAT - EXCEPT that ANY MODULES you want have the EXACT SAME PROBLEM! Prior to installing or activating the modules, you need to be able to access the command line (Unix) or other editors (Windows) to make the same change! Xoops creators and developers need to REMOVE the TYPE=MYISAM options and let the database use whatever the default is for that installation! Xoops would be the BEST SYSTEM I HAVE SEEN and I would USE it if I didn't have to keep correcting this one error for EVERY PART that I wish to utilize! |
| Re: Database problem |
| by CeroKool on 2009/10/21 21:34:26 Except the delete part. Rather, I just didn't extract those files in to the htdocs in my local machine. But for some reason i couldn't install XOOPS directly from 2.3.3b. That is why I went the not-so-long way. So, yes, I made 2.0.18 in to 2.3.3b upgrade ready. Uploaded it. Installed. And upgraded it. With out having to upload anything else. Finally: - mainfile as read only - delete upgrade & install folders |
| Re: Database problem |
| by ghia on 2009/10/15 1:12:48 If I got this right, you were using the install directory from 2.0.18? (because the 2.0.18 packacge has be combined with these files from 2.3.3: 1. Move the "upgrade" folder inside the "htdocs" folder (it's been kept out as it's not needed for full installs) on your local machine 2. Delete htdocs/mainfile.php, htdocs/install/, htdocs/cache/, htdocs/extras/, htdocs/template_c/, htdocs/themes/ and htdocs/uploads/ from the "htdocs" folder on your LOCAL machine ) |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|