Tyssen

Does LoginRegisterPro give you the ability to have different register forms for different roles? Or if not, is there another way to do it?

OK, understood. At the moment, it's being used on a feature which may not actually end up being actively used or by enough people to make it worthwhile fixing those sorts of issues. We'll have to wait and see.

9 hours ago, adrian said:

@Tyssen or use LoginRegister as a base (fixing the key Issues yourself)

Yeah, that's what I ended up doing, removed the restriction on the page-create roles.

I'm working on a site where I want people to be able to create listings but to do so they need to create accounts first.

For the login/register forms, I'm using https://github.com/ryancramerdesign/LoginRegister but it says in the module settings "Roles with page-edit permission are not shown."

But I want my new users to be added to a role with page-create/edit permissions for the template in question, so how do I assign that role to the module? Or is there another way I should be doing this?

@ngrmm I did what you suggested and installed the new module locally. It has more fields on it than the old one and I tested adding settings specifically to the templates for the pages that are missing and then added a priority of 1 to them which seems to be the only thing I can do for when they're not showing (the rest of the options are for hiding pages that are in the sitemap), but I still don't get the pages showing.

The way things are set up is like:

- Shop
--Categories
---Category 1
---Category 2
--Product 1
--Product 2

So the /shop page and all the products directly below it show up in the sitemap, but the /shop/categories page and all its children don't show.

I can't see anything in the settings for the templates for the categories or the children or the pages themselves that should be hiding those pages.

11 hours ago, ngrmm said:

@TyssenMaybe the old module has also these fields.

No, the old module doesn't have any fields. The only thing I can do is uninstall it. And I can't even do that because when I try I get:

Quote

Argument 1 passed to ProcessWire\Fields::___delete() must implement interface ProcessWire\Saveable, null given, called in /wire/core/Wire.php on line 397

@zoeck the parent page and its children aren't hidden and none of them have a sitemap_ignore field added to them.

I've inherited site that uses Markup Sitemap XML for generating the site map but there's a certain group of pages that are missing from it and I can't figure out why.

There is a checkbox field for hiding pages from the sitemap but it's not actually assigned to any templates.

There is no sitemap-xml.php file or anything like that.

I've looked in ready.php and there's nothing in there related to sitemaps.

Where else should I look?

27 minutes ago, bernhard said:

Where did you find this link? It's from an older version. I renamed the profiles at some point: https://github.com/baumrock/RockFrontend/tree/main/profiles

https://processwire.com/modules/rock-frontend/ under example _main.php

@bernhard that looks cool, I'll check it out more closely. BTW, https://github.com/baumrock/RockFrontend/blob/main/profiles/rock/files/site/templates/_main.php is 404.

Does anything like https://github.com/clubstudioltd/craft-asset-rev exist for PW?

I create a manifest.json file using my build process, which contains code something like

{"css/app.css":"css/app-65445d4baa.css","js/app.js":"js/app-889f5dca36.js"}

and then in the template I'd have

{{ rev('css/app.css') }}

which replaces that with whatever is in the manifest file.

Thanks @DV-JF that works great! ?

So no way to do it without having to fiddle around with extra fields? It's not that important if the field still shows, so if there's not a simple straight forward to do, I'll leave it as is.

Yes, that's what I've already been looking at. What I don't know is what selector to put in the show-if dependencies field. If it was a checkbox it would be checkbox_field=1 but I don't know what the format should be for repeater matrix fields.

That would be on the front end. I was talking about the field settings so that the old field doesn't show in the admin if the new field has content. 

I'm upgrading an old PW site which originally just had a single body field and now giving them a repeater matrix field which will allow more types of content.

For the template, if the repeater matrix field has content I want to hide the old body field from the editor. What would be the conditional that I'd enter into the settings for the body field? I thought it might be something like matrix_content.count=0 but that doesn't work.

Not necessarily. Page title might be terms and conditions, but you don't really want the page name being /terms-and-conditions/

Yes, that was it, thanks. I'm not totally familiar with how the site is put together yet, but I think the issue may be that there are hard-coded links to some pages in templates.

I've inherited a PW site that has something installed which forces changes to the page title field to update the page name field under the settings tab too, and vice versa.

The site does have the Connect Page Fields installed but title and name aren't set as connected fields. It also has Custom Inputfield Dependencies installed but that doesn't look like it would do this.

Anyone have any other ideas what might be causing it? Because I'd like to turn it off.

Sorry, my memory's not great and I have no idea which project this relates to now. Although it probably involved not using the module in the end and doing a more manual process.

Actually, it seems like probably something else going on with my set-up. I changed some things to fix a different problem, tried re-enabling Tracy, and it's fine now.

I should mention that I get that error in the admin area. If I disable Tracy and then change PHP version to 8, then the admin works OK.

When changing PHP from 7.4 to 8.0 I get this error pointing to line 1155 of TraceyDebugger.module.php:

if(in_array('titlePrefix', $this->data['styleAdminType']))

Opening the call stack says that $haystack = 'default'.

I'm running PW 3.0.210 with Tracy 4.24.3.

Not sure whether this is a problem with the module itself or something else in the site.

It turns out that this was the missing piece:

curl_setopt($cURL, CURLOPT_USERAGENT, 'Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0');

2 minutes ago, flydev said:

And to be sure, you can try the code above on a mock server:

// $url = 'https://json-api-url-domain.com/matches?id=XX&division=YY&teams=[ZZ]';
$url = 'https://my-json-server.typicode.com/typicode/demo/comments';

With pw, or not - should give you a resource ok message, a 200 http code, with an array of two objects as a result. 

Yes, I get successful output with that. Still get 500 with your updated code on my URL.