Jump to content

Need to save twice in Admin?


Recommended Posts

OK, I have 3 simple textarea fields on my page.  Each contains raw HTML, no filtering.  If I edit the textarea and save it, it immediately reverts to the previous content and I have to edit twice and save twice. 

I think the issue is that I am testing a custom login screen.  I never log out.  I do however login again, and even though the login is successful, it refuses to save on the admin page.  Is this due to a changing session key or something?   Is there some way to work around this?   The whole idea was to be able to easily make edits, and every test basically logs me out without telling me I am logged out.

I get the same problem working in the admin interface.  Does it eventually time out the login?  I have been working on code in the textbox for awhile and it seems like if I wait too long to save, I get the login box and everything resets to the previously saved state.  This is basically what is happening when I test the login screen, except that since I'm logged in, I never get the login box.  It just fails to save and shows me the old data. 

Data loss due to these issues is extremely frustrating!  Any ideas on how to make the admin interface behave when logging in again or when it times out?

Link to comment
Share on other sites

Besides your workflow makes me feel a bit uncomfortable with all that raw HTML in input fields, and things like that, I struggle to really understand what pages you are looking at for changes you made and how you look at them and test them.

You mention the change of session keys, which only happens in case the session changes, which is rarely the case while working in the backend. There could be of course things like enabled developer tools in the browser, using a CDN on the website, and maybe even code you use in your custom login screen.

To make it clear:

Usually working in the backend should NOT take two tries to save a change. That's rarely an issue someone would face. I can happen, when for example you are behind a VPN (like in Opera, without knowing), cookie blockers, adblockers, and even a not so perfect setup of Cloudflare CDN that tries to cache everything in your backend.

To get you going:

  • is this a local or remote setup
  • if local: what kind of setup is that? (DDEV, Laragon, Docker, Custom)
  • can you post screens of your editing and testing pages (so we know where you actually are in ProcessWire)

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...