Welcome, Guest
Username: Password: Remember me

TOPIC: [SOLVED] Did Joomla 3.4.7 break DT Register?

[SOLVED] Did Joomla 3.4.7 break DT Register? 8 years 11 months ago #25277

  • jbannin
  • jbannin's Avatar
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 65
  • Thank you received: 2
What a relief. Updated Joomla to 3.4.8 and DTRegister to 3.1.6. Site seems to be functioning. Hopefully, I won't see any more malicious code injected into my Joomla templates. It's been an onslaught.

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

[SOLVED] Did Joomla 3.4.7 break DT Register? 8 years 11 months ago #25278

  • waynejb
  • waynejb's Avatar
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 131
  • Thank you received: 4
We had updated to Joomla 3.4.8 and DTReg 3.1.6. Able to get to registration form but now the template has disappeared and not longer visible. Its a form on a white page.
Part of the message is hidden for the guests. Please log in or register to see it.


Was able to resolve. Noticed that not in all cases was the Joomla sessions files being updated during the update process. Once I manually update the sessions files it worked normal.

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

Last Edit: by waynejb.

[SOLVED] Did Joomla 3.4.7 break DT Register? 8 years 11 months ago #25280

  • exx
  • exx's Avatar
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 9
  • Thank you received: 0
after updating dtregister to 3.1.6 with joomla 3.4.8
we get this error on the first page of event registration:

Warning: stripslashes() expects parameter 1 to be string, array given in .../administrator/components/com_dtregister/models/field.php on line 1520

any clue to solve it ?

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

[SOLVED] Did Joomla 3.4.7 break DT Register? 8 years 11 months ago #25285

  • AlexR
  • AlexR's Avatar
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 109
  • Karma: 1
  • Thank you received: 1
I have also confirmed the same issue exists for us as well. Both Joomla 2.x and 3.x sites are affected. Seems to be related to the recent security fixes recently published by joomla

Also, curious as to why this topic is marked as {SOLVED} :dry: - Nevermind! Saw the blog post :)

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

Last Edit: by AlexR.
Time to create page: 0.579 seconds