Forums

First, thanks very much for ChronoComments. I think it's great. However, I'm having errors resulting from conflicts with JEvents, and I don't know enough to figure the solution out. Here are the error messages I get when I click on the calendar (Jevents) to view an item:

Notice: Undefined property: stdClass::$id in /home2/pleasao9/public_html/plugins/content/ChronoComments.php on line 96

Notice: Undefined property: stdClass::$sectionid in /home2/pleasao9/public_html/plugins/content/ChronoComments.php on line 120

Notice: Undefined property: stdClass::$catid in /home2/pleasao9/public_html/plugins/content/ChronoComments.php on line 120

Notice: Undefined property: stdClass::$id in /home2/pleasao9/public_html/plugins/content/ChronoComments.php on line 120

Any suggestion is helpful. The JEvents forum has a comment by the designer, effectively saying that "the plugin is probably a "content" plugin that doesn't check that it is being called from an article but just assumes this."

Thanks!

Hi trlbldr,

Could be, or it could just be coding that doesn't check for all the variable declarations. Either way, these are just PHP Notices and are an irritant rather than a problem. Usually setting 'Error Reporting' in the site Global Configuration | Server Tab to one of 'SystemDefault', 'Simple' or 'None' will stop them from displaying.

Bob

Thanks, but no, changing the reporting to "simple" or "none" doesn't make the issue go away...There has to be a way to define the undefined properties. I mean, it's about the user's experience, isn't it? If the user has lots, or even one, such message thrown up (!) across his/her monitor, would that person likely stay? Or, would the visitor just move on more quickly than usual?

Cheers,

Don

Hi Don,

I agree with you - I'm not the coder here and I'm not a ChronoComments user. The fix I gave you works more than 95% of the time - I guess that you have an error level hard coded into your PHP setup.

I can possibly work out the code fixes needed to hide these Notices - would that be helpful?

Bob

Hi Don,

do you get these errors in an "article" page ? single article ? the id property should be defined for an article of course! let me know and I will give you more info!

Regards
Max

I'm getting the variable error in my module, using the latest 3.x version of Chrono engine.

It shows in the initial display of the chrono form module.

Hosting: hostgator.

Looking forward to a fix🙂

Thanks

Rowby

Hi Rowby,

This post is about ChronoComments, please post your errors in a new topic in Chronoforms forums!🙂

Regards
Max