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

TOPIC: Records Not Saving in BE

Records Not Saving in BE 8 years 3 months ago #26259

  • tagtools
  • tagtools's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 13
  • Thank you received: 0
On joomla 3.6.2, we are having an issue on 3.1.19, 3.1.10 and 3.1.11 where we click the save button in the back end and nothing happens. This is an intermittent issue and works maybe once out of every 4 times. Any suggestions?

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

Last Edit: by tagtools.

Records Not Saving in BE 8 years 3 months ago #26260

  • nathan.dth
  • nathan.dth's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 1857
  • Karma: 19
  • Thank you received: 218
We'd have to look directly at this. You are trying to save a manually created registration record in the backend... just to clarify? My first thought is that something is missing so validation is not allowing it to complete. A validation warning should give you a red X or something, but maybe that's happening but not displaying for some reason. There has to be something like that though blocking the Save ability. Again, we'd have to look at it.

Also, do you see any difference from one browser to another? Or from one admin template to another?

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

Nathan is no longer affiliated with DTH since the recent acquisition. You can connect with him and get any type of Joomla website help at www.JoomlaEmployee.com .

Records Not Saving in BE 8 years 3 months ago #26262

  • tagtools
  • tagtools's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 13
  • Thank you received: 0
We are using a lot of logic/conditional based on one field, which is choosing a registration type (25 different selections). Once they choose a registration type, it shows them additional fields based on their selection. This is happening on both built-in Joomla admin templates and it happens mostly on edited records, not manually created ones. On the back end, once a selection is made or changed for the registration type, it some times shows the conditional fields and when it does, it take a long time. Once the fields show and you make the edits to their registration record, it won't let you save the record. No red X's. We have other clients that use dtregister, but believe this might be based on the amount of "logic"/conditional fields that this client uses.

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

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