Jump to content

Can't publish user: Saved Page: /admin/access/users/test/ - Cannot be published until errors are corrected

Recommended Posts

This is a strange behaviour I'm getting, tried with v2.5.3 and now with v2.5.22.
I create a user, enter all the details including correct password, click on publish and I'm getting this error message:
Saved Page: /admin/access/users/test/ - Cannot be published until errors are corrected

I tried to delete the user and recreate it, create a different user name, no luck.

I' can't figure out what is wrong as this is supposed to be a pretty simple task to do and there's no topic on this error.

Edit: This user "test" was working before but now is unpublished

Could someone please direct me to the right direction? Thanks

Share this post

Link to post
Share on other sites

That's weird indeed.

Is there no other message above the notice that you mention? Did you install a module that hooks into ProcessPageEdit or maybe ProcessUser?

Share this post

Link to post
Share on other sites

Create a new user (jjosi3), do you still have the same problem?

Share this post

Link to post
Share on other sites

I have seen that error when fieldtype doesn't match input or a required field is empty, but it generally informs me what field was the problem (with a big old red notice on top of the field too). So that's weird that you're not getting any description of the problem.

If you haven't added any of your own fields to the user template and have checked/double-checked the input of every form, here is what I would do :

1. turn on debug in /site/config.php and see if it gives any extra information

2. If that fails, search the code to see where it outputs that error. (Only one place: https://github.com/ryancramerdesign/ProcessWire/blob/676458407bd530b69b50c6ef2f44cf16e4ef4449/wire/modules/Process/ProcessPageEdit/ProcessPageEdit.module#L211) Based on that it's safe to assume you have some formErrors. Look a few lines before that (L195), I would temporarily change

$formErrors = 0;
foreach($this->notices as $notice) {
    if($notice instanceof NoticeError) $formErrors++;
$formErrors = 0;
foreach($this->notices as $notice) {
    if($notice instanceof NoticeError) {
        $this->error('Notice: '.$notice);
That might give you a clue about the notice that is causing a formError. Once you get that info (or even if you don't), you should undo the changes you made to the module file. Anyway it's a hack, but it's how I sometimes investigate what is happening...
  • Like 3

Share this post

Link to post
Share on other sites

Thanks for everyone for the responses, I couldn't check back in the meantime.

As a workaround I got around the problem by creating the user in the API and it worked like a charm.

Deleting/recreating the user  in the backend didn't help, even when using a different username.

The strange thing is that there are not that many fields on the standard user form so I could hardly miss anything.

There were no other error messages on the top of the page or in the error log, just simply didn't work.

If I have time I'll get back to it to further investigate using the suggestions.

Sorry to abandon the topic, I haven't got any notifications and I had to rush to meet the deadline...

Thank you all for the help, I really appreciate it and will come back with my findings.

Share this post

Link to post
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

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By neonwired
      I'm hoping someone has seen this before. There doesn't appear to be an issue with the user info.


    • By prestoav
      Hi there,
      I have a marketplace site that used the older Fredi module for front end editing so advertisers can create and edit their adverts (in the form of pages). After upgrading to v3.0 of Processwire I'd like to change the editing method for users to the new, core front end editing methods. However, it seems that with this method any editor can edit any page (subject to template restrictions for their user role). Using Fredi I checked the user and created user were equal before displaying edit buttons (clunky but it worked).
      Is there any stock way to restrict front end editing to the creator of the page so that my advertisers can only edit their own ads or should I test for user as before?
      Thanks in advance as always 🙂
    • By DooM
      Hey guys!
      I try to achieve a possibility for the client's admin account to change other users privileges. 
      In the CMS I have superadmin account, which is for me. My client got an account with a role user, which is limited administration account. The client also got some other people, who will edit the content with role editor  
      User story would look somehow like this:
      user role can add new roles and users user role can change privileges for all users (except superadmin). Eg. When the user role gives the editor role privilege to edit only articles. The Editor role will be able to edit only them.  
      I know this functionality is possible for superadmin, but I couldn't simulate it on the user role. Is there any easy way to achieve such a feature? Otherwise, I'll have to make a module for this I guess.
      Thanks for any help!
    • By Marcel
      I am about to use the tool Create Users Batcher. We have 450 users. When I tryed it with like 20 test users it worked but it took a while. Now my concerns are that 450 might be to stressful? Does anyone have experience with several hundreds of users? My thoughts are to split it in smaller goups and upload them one group after another.
      best wishes
    • By louisstephens
      So, I really don't know where to begin with this. I have the thought in my head (the basics), but not really sure how to set it up.
      The desired effect:
      The homepage is set up with a foreach loop that outputs all the child pages (basically just a bunch of pages with pdfs, docs etc stored in a file field). When A user is actually logged in, they can "star" an item or drag and drop (using Dragula) the page to a sidebar. Also, they would be able to reorder the pages in the sidebar.
      The question(s):
      I guess I have multiple questions regarding how to achieve this.
      Would it be best to create a page field in the user template to save the page(s)? How would you actually save the page state (sidebar output, reordering, etc) once the drag and drop has been used? Thanks in advance for any help! A lot of this was just what was in my head, so it might not make full sense. However, I will update this if I can actually wrap my head around everything.
  • Create New...