I left a nasty bit of debugging in the module which I have just now taken out. If you downloaded 1.6.1 prior to now please download this updated version that removes the debugging.
should really change the version # or add a revision character like 1.6.1a
When I was trying to restore mysql database of joomla (with SMF) using phpmyadmin, I go the following error:
SQL query:
CREATE TABLE jos_components(
id int( 11 ) NOT NULL AUTO_INCREMENT , name varchar( 50 ) NOT NULL default '', link varchar( 255 ) NOT NULL default '', menuid int( 11 ) unsigned NOT NULL default '0', parent int( 11 ) unsigned NOT NULL default '0', admin_menu_link varchar( 255 ) NOT NULL default '', admin_menu_alt varchar( 255 ) NOT NULL default '', OPTION varchar( 50 ) NOT NULL default '', ordering int( 11 ) NOT NULL default '0', admin_menu_img varchar( 255 ) NOT NULL default '', iscore tinyint( 4 ) NOT NULL default '0', params text NOT NULL , PRIMARY KEY ( id ) ) TYPE = MYISAM MySQL said:
#1064 - You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'option varchar(50) NOT NULL default '', ordering int(11) NOT
I tried this at two different hosting places and got the same error. So we can rule out the hosting places' fault.
Any body know what would cause this error and what should be done in this situation?
Thanks.
SH*T! I just realized something....look at your code (in RED) ..notice the word option is "OPTION"?? That seems like you were trying to create a field OPTION which is a RESERVED WORD in mySQL see http://dev.mysql.com/doc/refman/5.1/en/reserved-words.html
you HAVE to backquote the word OPTION like this `OPTION`
If it is just THAT table you have to worry about, maybe you can take the create table code from the script and just use the INSERT part of it to populate the table?
Or, if you messed up the structure of the table, rename the existing table (I'd suggest baking it up but that doesnt seem to be our thing right now ) and CREATE A NEW TABLE building it to the specifications outlined then using the INSERT bit of the code like I said earlier...
If this works, then edit your original post adding [FIXED:] to the topic
I'm not sure you should - those '[' and ']' are also used in BBCODE in the forums, and ShoutBox and as delimiters by other PHP program. GPL development you tend to have code coming from all over the damn place with God knows what coding standards and checks in place - MagicQuotes on yes/no etc.
maybe you could post an example of what the id they would want to use exactly and we could maybe do a workaround or suggest something else..
BTW, can they use "{" instead of "[" ??
also can they 'escape' the character by typing \ before it?
Nice! I've applauded that nice little tidbit (and adding one of my own .. http://www.troozers.com/joomla!/howto/hidden_login_box.html )
This will allow you to have a POP UP Login Box.. very cool..you can also use this technique to have other content just pop up when you want!_
Now peter, go back and edit the title of your post and add [FIXED] that way, people KNOW the problem was resolved and that people who are searching for fixes will find this more easily.
Where is the web page in your Joomla environment, or is it somewhere else?
You could put the document in DocMan and then cut and paste the download link for it into your web page (That way you can take advantage of the Anti-leech and download tracking features of DocMan, and, if the file updates in place you don't have to change your link)
Why is everybody allways sounding so damn surprised??? :<(
Three different means of login in to an app and you are surprised when it breaks??.
We need to have ONE STANDARD LOGIN/LOGOUT MODULE
(and then couple that with a standard function that will return the UNIFIED LOGIN STATUS and replace the calls that CB, SMF, JOOMLA use with a call to that bot/module/class/crap )
If you have SMF buy itself, you expect to use the smf login, ditto for Joomla or CB, you integrate all 3, (or 4,5 if you add OSCOMMERCE, Coppermine )etc then you have login logout hell.
You need a traffic Cop that coordinates the access requests and it is st$p$d to think/code otherwise!
(aaaahh, felt good getting that off my chest - and onto yours!_
...yes... I noticed that I didnt help y'all much one way or another...but I helped me! Boy, do I feel GREAT! Happy New Year Everybody!
No offense taken, I know I PM'ed you before about my issue with my hosting and we talked about the option of going dedicated. Just to clarify for those who might make an assumption. MamboServe.com is NOT my host. They're one of my affiliates.
...8-Snipped-<---
MamboServe.com is NOT my host JEEZ I am so happy to hear that (and they must be too!) I can't tell how many times this site has been offline,online but quirky,"no site configured at this address", or just plain slow
But, for the life of me, I can't figure why this little site would need a so called "dedicated server" ? I mean, there's not THAT much traffic/bandwidth utilisation is there?
I know that SMF makes some recursive calls to clean input that taxes servers (and crashes some,depending on the version of PHP etc.) but the SQL utilisation is modest.(well the bridge does add a little overhead checking too user tables for every authentication).. The biggest culprit I've found is Remository causing me to switch more happily to Docman
My understanding from what I read in this forum ( I don't why I looked it up -I must have been drunk as it's a lot simpler to just ask!) is that it adds to SMF if you are logging in from Joomla and vice versa if you are logging in from SMF (assuming that your login existed previously in the component you are login in from.)
What you did seems perfectly safe and, is what the content_bot does! (of course, with the bot, you can change it from the backend, but your way means you have to change the template file - for each template you use.)
but is does work as you've seen!
The "<?php" and "?>" signify to the browser, Hey jump out of what you are processing (HTML) and work on this PHP code.
The area that you were working on was ALREADY PHP code, so that's why it caused the problem (which you smartly fixed!)
Joomla Hacks is a Joomla Components, Joomla Modules, Joomla Templates, & Joomla Mambots resource portal. None of the text or images in this public website may be copied without the expressed written consent of the authors. Copyright 2005 by JoomlaHacks.com. Powered by Joomla. All rights reserved. Terms of Use