not compatible with mx comment

chrono forms kick out an error in line 161 of the mxcomment mambot

seems that this should be fixed here and not on the mxcomment side as mxcomment has been around for longer

Hi swacks,

Line 161 of maxcommentbot.php in mXcomment v1.0.5 reads

$moduleLoading = $params->get( 'pdf' );

it seems pretty unlikely that this will give a conflict.

Please can you be more specific about which version of mXcomment and which of the three mambots in it?

Bob

Fatal error: Call to a member function on a non-object in /home/topbil00/public_html/mambots/content/maxcommentbot.php on line 161

sure, this is the error , the funny thing is that it initially the error doesnt come up ,but after a few page refreshes between an artricle with the mxcomment bot and form bot then it comes

there is an article with chronocontact bot here form

and an article with mx comment here
mx comment 1.05 (components and bots)
chrono 2.35
chrono contact 0.4<br><br>Post edited by: swacks, at: 2007/11/04 15:54

Hi swacks,

I've refreshed and rated on both pages a dozen or more times without seeing the error message :-(

I can only guess that something odd happens with the global 'pdf' parameter . . . perhaps Max will have a better idea.

Bob

Hi swacks,

Say you tried this with Firefox, try it with IE, after how many refreshes you get this error ?

and I think if this error really exists then it won't be a Chronoforms issue at all, the error shows that the error is in mxcomment file, do you have both bots loaded at the same page ? which one is loaded first ?

Cheers

Max

the error does exist. Its on our subscription page (running chronoforms) so if you email me i will turn on mx comment so you can see the error live.

look - not trying to force you here , but if i cannot run mxcomment i will have to find another form . Mxcomment is the best comment component and has been around for a while , whilst although chronoforms is excellent , i can duplicate it a form fairly easily, so i think its fair comment for me to say that you guys should make your component compatible with leading components

Hi swacks,

I didn't say mxcomment is bad, I only said that the error is at the mxcomment file not chronoforms🙂

Could you please send me the file pointed to at the error ? please attach it here!

Thanks!!

Max

Hi Max,

Here's the file.

Bob [file name=maxcommentbot.zip size=4757]http://www.chronoengine.com/components/com_fireboard/uploaded/files/maxcommentbot.zip[/file]<br><br>Post edited by: GreyHead, at: 2007/11/06 12:42

Thanks Bob!!

Can somebody help me on removing the footer of mxcomment

Hi cooljohn,

Can you give me a clue what mxcomment is and what the problem is?

What footer - where? Maybe post a picture.

Bob

Bob... mxcomment has a copyright footer which looks really bad on sites.. it would help everybody if you find out how to remove mxcomment's copyright footer.....

the footer goes here...
mXcomment 1.0.8 © 2007-2008 - visualclinic.fr
License Creative Commons - Some rights reserved

Hi cooljohn,

I'm not certain but try commenting out this line

_getNoticeCopyright();

each time it appears in maxcomment.html.php - there are several of them.

Bob

I deleted all the_getnoticecopyright ones
but.. it didn't work....
can you plz plz suggest something else to get rid of that footer....

Thanks for your concern.....

I deleted all the_getnoticecopyright ones
but.. it didn't work....
can you plz plz suggest something else to get rid of that footer....

Thanks for your concern.....

i commented out all the _getNoticeCopyright(); in that file. but it still shows that note..Kindly help me.

Hi vastal,

You've got my best suggestion already - please ask at mxcomment support.

Bob

I got past the mxComment footer problems today. If you want to know how then read the code in the attached file. Or just replace the same files in the extension and it will go away.

[file name=maxcommentpatch.zip size=11143]http://www.chronoengine.com/images/fbfiles/files/maxcommentpatch.zip[/file]

Hi michpeta,

Well done - I see that the answer is "ZWNobyAkbm90aWNlQ29weXJpZ2h0Ow0K"

Bob

Thanks,

the real answer was to decode the string using base64_decode and echo it out on the screen.

They hid thier code to stop this from happening but they also didnt allow anyone to purchase a "clean" version from them. I have purchased many extensions and would happily have purchased thiers also if they allowed it. I believe this is a grey area ethically however I believe it was released under the GNU.

Not sure what path I could have taken differently.

Hi michpeta,

I think that base64 encoding is probably OK. It stops the casual browser from doing anything but if you know any PHP it can be broken in a few seconds.

Bob