Recently Browsing 0 members
No registered users viewing this page.
when you add a page you can see the page name of the page under the page title field. But when you change the page title afterwards, you have to go to the settings tab to also change the page name.
We have many clients that change the page title afterwards but forget to change the page name, because they don't look in the settings tab or forget it.
Is it possible to show the page name on the content tab under the page title?
I hate to say this, but I like how WordPress handles this better:
Or should I open an GitHub request?
By Robin S
Pages At Bottom
Keeps selected pages at the bottom of their siblings.
A "bottom page" will stay at the bottom even if it is drag-sorted to a different location or another page is drag-sorted below it (after Page List is refreshed the bottom page will still be at the bottom).
Newly added sibling pages will not appear below a bottom page.
The module also prevents the API methods $pages->sort() and $pages->insertAfter() from affecting the position of bottom pages.
Note: the module only works when the sort setting for children on the parent page/template is "Manual drag-n-drop".
Because you want some pages to always be at the bottom of their siblings for one reason or another. And someone requested it. 🙂
Install the Pages At Bottom module.
Select one or more pages to keep at the bottom of their siblings. If you select more than one bottom page per parent then their sort order in the page list will be the same as the sort order in the module config.
I'm trying to build a bitwise filter for a database query for my textformatter module, and I stumbled over some page statuses I don't quite understand:
/** * Page has pending draft changes (name: "draft"). * #pw-internal * */ const statusDraft = 64; /** * Page has version data available (name: "versions"). * #pw-internal * */ const statusVersions = 128; If I'm not mistaked, there's no way to create multiple draft of a page in the ProcessWire core without module, is that correct? I initially assumed was the status assigned to unpublished pages, but the unpublished status corresponds to id 2048. Is the only way to create drafts with the ProDrafts module?
For my purposes, I just need to understand how I should treat those statuses. I'm trying to get all pages that are published and either hidden or not hidden (I want to make this configurable). Do I need to exclude pages that have the statusDraft, or statusVersions? Only one of them? Only in combination with other statuses? Or can I safely ignore those (so it's fine if the pages have the status or not)? I don't own the ProDrafts module, so I can't check the code to see how individual drafts are stored and how the draft ids correspond to the published id.
Any insight into those statuses is appreciated. Thanks in advance!
I have a user page template with many fields that are organised in tabs. Tabs do not work on the profile edit screen. So I had to find a way how to let users edit their page with tabs in place.
The way I solved this is having users edit their user page in the backend instead of their profile page. So basically they are on a page edit screen and not on their profile edit screen which is a different process. The drawback of this method is that the users edit their profile on a URL like .../youradminurl/access/users/edit/?id=1377. So I needed to make sure that users cannot edit other users' profiles by just switching out the id. I did this through hooks that redirect them to their own profile.
This is far from a perfect solution. Ideally I would like to mask the page edit url to something like /myprofile but haven't found a way on how to do this, yet.
How would you go about this?
redirect rules in .htaccess hooking into the profile edit process? Either way I couldn't figure out how to accomplish it. Any pointers towards a solution would be very much appreciated.
Reference: PW 3.0.111 and uikit3 based site using the Regular-Master profile.
I've setup a page where a member can edit contact details via the frontend displaying the field content using the <edit> ... </edit> tags.
This works fine when the fields actually contain data. However fields that contain no data (i.e. empty) do not appear to be editable. No edit cursor appears (- possibly owing to the field width being 0px?)
Is the only solution to recreate the page using a form, for example, or is there a simple way to allow blank fields to be editable on the frontend?
I wondered if anyone else has found a solution to this problem. Any assistance would be appreciated.