I understand the feature request there, and there are technical reasons its not that way at present. I would ask however, if they are for applications, wouldnt you be best to just rename the field to "Full name" or something similar?
Thank you. I have attached that here, hidden, so my colleagues can see the issue in action. To be honest, personally I cant see how we could affect that, however of course Im not one of the developers
Unfortunately, the only thing I can suggest at present is upgrading. There has simply been too much change to be trying to manually change items with code from today's release. There will have been thousands of bug fixes since that point in time, and quite a few major changes to the way things work
I think you have probably answered your own question there. They need to upgrade to the latest release of the platform. The reality is, they are using a version that was released in 2019
Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
Could you please let us know the next time you have one of these, and take note of the details there, then let us know. We would need this in order to proceed
We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section.
We look forward to further assisting you.
Unfortunately, its difficult to know what could be causing the issue without being able to see it. What you mention above, would actually also point to it being an issue with permissions, as the logs folder would generally contain the error
As mentioned, the second item you would add as a suggestion. The latter you have stated you won't go into detail on, so I'm not sure what we can do to assist you unfortunately.
Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
The likelihood is, something isnt able to be written somewhere, so check permissions on folders. You may also find errors logged in uploads/logs that will give you a better understanding. Clearing the datastore folder is another thing you could try
We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section.
We look forward to further assisting you.
Sorry, we would need more information. We need to know when it was scheduled for, when it actually showed, and an example user it was showing to before published (along with where it was actually showing).
Now you have done, go to support in the admin CP and see if there are any issues showing under the mysql section. If there are, I would advise on resolving those to prevent issues in the future