Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: [SOLVED] Fatal error: Cannot access empty property in ...

[SOLVED] Fatal error: Cannot access empty property in ... 13 years 4 months ago #14356

  • torbonaut
  • torbonaut's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 3
  • Thank you received: 0
Hi,

I am using DT Register 2.7.7, Jomsocial 2.0.0 and AEC... when registering for an event in frontend (as registered user) following message appears:

Fatal error: Cannot access empty property in .../administrator/components/com_dtregister/models/jomsocial.php on line 74

Server Data:
PHP 5.2
Joomla 1.5.23
MySQL 5.

Thanks for your help.

Please Log in or Create an account to join the conversation.

[SOLVED] Fatal error: Cannot access empty property in ... 13 years 4 months ago #14465

  • torbonaut
  • torbonaut's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 3
  • Thank you received: 0
Can somebody please help... have not received an answer yet?

Please Log in or Create an account to join the conversation.

[SOLVED] Fatal error: Cannot access empty property in ... 13 years 4 months ago #14466

  • andybon
  • andybon's Avatar
  • Offline
  • Gold Boarder
  • Gold Boarder
  • Posts: 239
  • Thank you received: 0
I could be wrong but I think the first official response would advise you to upgrade to 2.7.8 and see if the problem remains....

Please Log in or Create an account to join the conversation.

[SOLVED] Fatal error: Cannot access empty property in ... 13 years 4 months ago #14487

  • torbonaut
  • torbonaut's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 3
  • Thank you received: 0
Thank you very much... will try : )

Please Log in or Create an account to join the conversation.

[SOLVED] Fatal error: Cannot access empty property in ... 13 years 4 months ago #14488

  • dthadmin
  • dthadmin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 5470
  • Thank you received: 3
Sorry there was no initial reply here. Andy is right though. This was actually fixed in one of the 2.7.7 update packages. But upgrade to the current and the error will be gone. Thanks.

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Time to create page: 0.651 seconds