Cant publish role

[Peter Knight]

Hi guys

Having problems publishing a new role.

I can create it, tick the permission checkboxes and hit publish.

Once I return to the Roles overview page, the role remains unpublished.

I'm preforming this action as a super-user with full permissions so I should be able to achieve this.

As all things PW-related are pages, I tried too to drill down through the page tree and directly manipulate the page under 

Tree > Admin > Access > Roles

No joy there either.

This is on 2.7.3 dev. Nothing in the error logs and I have a few sites based on this site in exact same environment with no role problems.

Any tips?

[Martijn Geerts]

[Peter Knight]

Hey Matrijn

I'm not sure what you mean. 

I've tried publishing this page directly from the page list / tree and had the same result.

Is that what you meant?

P

[Peter Knight]

I haven't fixed this but I might be making progress.

I get a brief error message when I try to publish the editor role

Saved Page: /processwire/access/roles/editor/ (1 change) - Cannot be published until errors are corrected

The only actual error is the persistent

Unrecognized HTTP host:'www.your-website.com' - Please update your $config->httpHosts setting in /site/config.php - read more

I've tried everything to resolve the host problem:

• delete the sessions folder
• deleted the cache folder
• checked and double checked the confi files in both site and wire folders
• removed the Config module

It's a persistent bugger :-/

[Soma]

Have you entered your host in the config?

[LostKobrakai]

Wondered about the same thing a few weeks ago. It's just not clear enough that an error, which pops up on each request and leaves things mostly functional, does prevent publishing of pages. 

https://github.com/ryancramerdesign/ProcessWire/issues/1759

[Peter Knight]

Have you entered your host in the config?

Yep. I added it to the config, uploaded, checked it was online.

I've even removed it and then tried some forum tips of removing the host from the config completely.

I've tried manually updating the config file in /wire/ too.

Pretty much tried everything 

[Soma]

Well this message, behaviour and error only shows if your domain isn't in the hosts config.

[Peter Knight]

Well this message, behaviour and error only shows if your domain isn't in the hosts config.

My screengrabs disagree ...

My /site/config.php file

My config settings in the Config Module

The only other place that httpHosts is set is in /wire/config.php and that's blank / default.

This is a site I based on another site by doing a crude file and database copy and it has the same $config->userAuthSalt setting.

I wonder could that be a cause? 

[Soma]

I'm not sure but I think protocol isn't needed here (http/s).

[Peter Knight]

I'm not sure but I think protocol isn't needed here (http/s).

I think you're right. I just added that in before I took screen grabs. Removing has no effect.

[Soma]

Just to make sure, this doesn't have anything to do with roles, you can't save anything else too? Well I don't know, since the message shows up, the problem lays right there. Maybe somehow your host resolved is different than what you enter.

[arjen]

What if you disable the config module and just use the /site/config.php? Have you entered the domains in both?

Also, you might want to check if ProcessWire (or PHP) is able to get the proper hostname. I had one case (on a shady server, long time ago) where PHP didn't recieve the proper hostname so ProcessWire kept telling me that I needed to update the hostname.

[Peter Knight]

What if you disable the config module and just use the /site/config.php? 

Removing the entire Module doesn't work. The error persists.

However, I noticed that you can leave the Module installed but just remove the offending config setting.

That worked

[arjen]

Glad you got it working.

Removing the entire Module doesn't work. The error persists.

You could check if the config.json file still exists in your /site/assets/config/ folder. And be sure to remove this code from your /site/config.php.

[Peter Knight]

Glad you got it working.

You could check if the config.json file still exists in your /site/assets/config/ folder. And be sure to remove this code from your /site/config.php.

So am I. I love getting editors their access and seeing them update their PW sites. Great to have this solved.

I don't think I need to remove that code from site/config.php as I'm still using the Module for a few settings

"defaultAdminTheme": "AdminThemeReno",
    "debug": false,
    "adminEmail": "peter@net.not"

I've just removed a particular config within the config module.

[arjen]

So am I. I love getting editors their access and seeing them update their PW sites. Great to have this solved.

Regarding this business: next to payments the best feeling in the world

[tpr]

Fixing the config is universally a good thing

[Peter Knight]

Just a quick update on the above in case anyone else runs into problems with this.

Having had the solution work for most sites, today I had a persistent "unrecognised HTTP host" message even though 

• config module was uninstalled
• congig settings were correct
• caches were cleared 
  etc

As soon as I fired up the same site Admin in a different browser, the issue disappeared and I could publish roles etc.

In this case it was Google Chromes cache caching my old config files.

Over and out !