Who's Online
We have 39 guests and 4 members online
|
Conflict With Other Component (1 viewing) (1) Guest
Favoured: 0
|
|
|
TOPIC: Conflict With Other Component
|
miniad (User)
Fresh Boarder
Posts: 5
|
|
Conflict With Other Component 1 Year, 10 Months ago
|
Karma: 0
|
|
Not sure if you would call this a bug, but thought it was worth mentioning. There seems to be a conflict when using this module with the Sobi2 directory component. For some reason anything entered in the Sobi2 form in a text area field is lost whenever the MiniAd module is published.
Once I published the module I noticed entries coming in from users lacking any descriptions (the text area field). All other input fields were fine and the data was saved. I never put the two together until I started doing some testing. I have no clue why this happens but thought it might be good to let you know just in case other users are running the Sobi2 component.
If I can determine what is causing this I'll update this post. Any suggestions would be greatly appreciated. I really liked the module and hoped to use it, but will be unable to until I get this glitch figured out.
Best regards,
Pete
Just an FYI...I'm running Joomla 1.0 and the lastest version of MinAd 1.1.
|
|
|
|
 Logged
|
|
|
Last Edit: 2008/09/07 00:43 By miniad.
|
|
|
The administrator has disabled public write access.
|
|
|
|
Re:Conflict With Other Component 1 Year, 10 Months ago
|
Karma: 8
|
|
Do you have the latest version of Sobi2 2.8.7.2
Do you use sh404SEF ?
You could try disabling it.
Have you tested using different browsers?
If your sobi2 menu module is enabled it may cause errors for other modules. Try unpublishing your sobi2 Menu module.
|
|
|
|
Logged
|
|
|
The administrator has disabled public write access.
|
miniad (User)
Fresh Boarder
Posts: 5
|
|
Re:Conflict With Other Component 1 Year, 10 Months ago
|
Karma: 0
|
|
Yes, I am running the latest Sobi2 version and I am not using sh404SEF. I've tested it using Firefox and IE. Sobi2 menu module is unpublished.....I don't use that for navigation.
|
|
|
|
Logged
|
|
|
The administrator has disabled public write access.
|
|
|
|
Re:Conflict With Other Component 1 Year, 10 Months ago
|
Karma: 8
|
|
Can you use the module on other pages where your component won't be used.
Did you try the script line after the <body> tag instead of before the closing </body> tag
I know people have managed to install this without having problems since the new release, its a shame it doesn't work across the board.
Cheers
|
|
|
|
Logged
|
|
|
Last Edit: 2008/09/09 10:58 By hiphopjam.
|
|
|
The administrator has disabled public write access.
|
miniad (User)
Fresh Boarder
Posts: 5
|
|
Re:Conflict With Other Component 1 Year, 10 Months ago
|
Karma: 0
|
|
Hello,
I took your suggestion and tried it after the </body> tag and it still had the same results. I can use it on pages where the component won't be used, but the majority of the website is based on the component. If it wasn't for that I would not even be worried about it.
I'll keep working with it to see if I can figure it out. If I find an answer I'll post it here. Really nice script though. Thanks for offering it as a free download.
If you have any other ideas let me know.
Thanks for the help,
Pete
|
|
|
|
Logged
|
|
|
The administrator has disabled public write access.
|
|
|
|
Re:Conflict With Other Component 1 Year, 10 Months ago
|
Karma: 8
|
|
The script line must be with in the body. Not outside the body. Try immediately after the opening <body> tag, not right before the closing </body> tag.
Also try the module without the script line to see if it is a tooltip conflict.
Best Regards
|
|
|
|
Logged
|
|
|
Last Edit: 2008/09/09 23:11 By hiphopjam.
|
|
|
The administrator has disabled public write access.
|
|
 |
|
|
Support Forum
