Jump to content
arjen

PageTable on user template isn't working as expected

Recommended Posts

Hi,

I got a PageTable which isn't working on the user template. As a superuser everything works fine. As an editor the page from the PageTable gets saved but the but the saved page won't show up in the PageTable field. When the superuser adds the page to the PageTable field the editor can see and edit the page.

No console JS errors. Triend two admin themes. Tried Chrome and Firefox.

The editor role has access to both user template (view, edit, create, add) and the home template (view, edit, create, add) and has the rights page-edit and user-admin.

. The PageTable config is:

  • 1 template pointing to a template with a title and a page field
  • I'm saving the pages under /data/

The funny thing is that when I move the PageTable field to a basic-page (or any other) template everything works as expected. When I move it back to the user template the problem is there again. It has to be some rights issue since it is working for the superuser.

I've setup an account with the latest dev where a simple install shows the problem:

http://bohrium-bwi.lightningpw.com/processwire/

user: editor

password: test123

Try saving the PageTable field on a user. I've added the PageTable to the basic-page too, so you can see it's working there.

user: superuser

password: superuser1

Any pointers or can anyone confirm?

Thanks in advance,

Arjen

Share this post


Link to post
Share on other sites

The issue is that the ajax response from "?id=1026&InputfieldPageTableField=pagetable&InputfieldPageTableAdd=1036" does not return the expected . It's responding with what seems like the body of the user edit page.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for the feedback LostKobrakai. Is this a bug or did I misconfigure something?

Share this post


Link to post
Share on other sites

That I can't answer. I think it's a bug, as it seems kinda useless to return the edit page itself instead of anything useful to be added to the table.

  • Like 1

Share this post


Link to post
Share on other sites

I've been looking into where the querystring originates, but I'm having trouble finding out. Any pointers to which file(s) the querystring is being build?

Share this post


Link to post
Share on other sites

I wouldn't necessarily think the query is wrong (can't compare as your superuser account didn't work) but rather the return value is not expected. The markup of the edit page shows up inside of the table.

Share this post


Link to post
Share on other sites

Thanks again. I updated the correct password.

Share this post


Link to post
Share on other sites

Whatever happened with this?

I'm getting the same issue, been testing with superuser up until now so all worked fine.

Now testing with a different role and I'm unable to access a custom page field in the user template.

Edit: It seems to depend on the type of page field.  I just changed to checkboxes and it works fine, still weird why it doesn't work with the other page field types.

Share this post


Link to post
Share on other sites

Martijn created an issue and we have tracked it down towards to the editable() function. We might be off, but when we disable this check the PageTable works as suspected.

  • Like 1

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.

×
×
  • Create New...