rick
-
Posts
635 -
Joined
-
Last visited
-
Days Won
6
Everything posted by rick
-
This is the only part where I wasn't scratchin' my head ? No. You may have multiple fields of the same TYPE, but you must have unique names, similar to files and file names within a folder. You can create a common field that is used within different templates, but you cannot use the same fieldname multiple times within the same template.
-
I'm not sure I understand your goal here. When you are coding your template files, Processwire sets $page to the current page. Therefore, the $page->id represents that page. I don't know why you would want to change the id. Or are you referring to a custom URL?
-
That is correct.
-
Hello @Pip, 1. Go to Setup > Templates and click the template you want to edit. Processwire displays a list of fields. 2. Click the Title field and enter the new title text you want displayed. 3. Click save. You can change any Label of any field in any of your templates to better suit your requirements.
-
The naming convention is actually the page ID, so 1234 in your example is the page whose id is 1234.
-
In your /site/config.php file do you have an entry that looks like this: $config->appendTemplateFile = "someFileName.php"; If so, then you can edit that file (in /site/templates) to replace the gtag entry. You may also want to check the /site/templates/home.php toward the bottom of the file. If not, then PM me and we'll go from there.
-
Okay, it appears that the gtag information is hard coded into the footer. You can copy the valid gtag data from google and replace the wrong data. Once that is done, you can re-verify through google. If that doesn't work, then let me know and we'll go the PM route.
-
Click the Templates item on the breadcrumb, then see what is in the basic_page template. Edit: If you would like for me to take a look, PM me and we can go from there.
-
So when you go to Setup > Templates and click on Home, what fields are listed? You may also want to set debug = true in your /site/config.php to display additional information while you get things sorted. You can set it back to false once it is working.
-
What template does the Home page use? ( Home > Edit > Settings) Check that template for the google fields, if any.
-
There does not appear to be a site settings type of page based on the pdf image you supplied. However, the gtag is in the footer of your site. Have you looked in the /site/templates folder for a footer.php file to see if it is hard-coded? edit: The <body> tag is in the wrong position also. edit 2: Welcome to the forum, @nwashburn!
-
It is a security risk by exposing the url to login to the admin side of Processwire to people that don't require access. Ah-ha! ? Everyone here has been at the starting gate, but I have trouble getting out of the gate. LOL. The first thing you should know is that Processwire is not like *any* other CMS/CMF. Specifically, the terminology may be confusing at first, eg, "Page". I would recommend that you read up on the getting started topics of this forum, and read the articles they may link to. I know, it's the boring part. Believe me, you will sleep better when you understand how PW works.
-
Hi @DaveC, Is there any reason you have the admin login link in the footer? If you are the only person logging in to the admin, then I would suggest you remove it. If there are others who must log in, then I would suggest you create your own login and redirect a valid user to the admin page.
-
Nevermind
-
Hi @Greg Lumley, Implementing a "user admin" on the front-end isn't difficult because of PW's API -- In theory, that is. If you aren't familiar with PHP, or aren't familiar with the API, then it obviously will be a little more difficult. You can ask any questions here in the forum and a plethora of highly-skilled programmers will be glad to help. That's another big selling point with PW vs any other. The community support is second to none. The following is an example break-down of one of my sites. I have one site where specific users have the only permissions to access specific pages. All other users could only view pages. Think of it like the *nix RGE permission structure, where Root is super user, Group is any registered user, and Everyone else is a guest just visiting. PW initially gives you the Root and Everyone roles, so you will need to add the Group role. You can name it what you want. And since I don't let *any* user access the PW admin, I don't need to specify any permissions, such as page-edit, etc. I use Processwire's built-in page management to further limit a user to only their pages. Specifically, all pages have a created_users_id, and other information that is saved each time a page is created or updated. So when a user wants to create a new entry (page) their $user->id is assigned to the created_users_id property. Now I have a one-to-many relationship between a user and all of their pages. I also have different sections where a user can create a page. For example, when a user logs into my site acme.com, they can create a page under "high-explosives", and another page under "jet-powered devices". They may not wish to create a page under any other section. Each section has it's own template, so I can easily use selectors to retrieve the user pages by section, or even retrieve all pages. The front-end "user admin" interface is simply a two column layout with a menu on the left and the content on the right. I use the Group role to determine the menu options. I obviously don't want one user viewing details of another user, except for me as super user (Root). This also restricts the admin page(s) from view by the Everyone (Guest) role. I also have a drill-down capability from this initial user admin page to get more specific details. Each user can manage their own personal data page as well. That is the basic overview. The next thing are the modules. If you do not have your own login system then I would recommend LoginRegisterPro as it covers all the bases (register, login, forgot password, etc.) that you will need for your user access requirements. I am currently looking into implementing @bernhard's RockFinder3 module to handle queries because I have many users and they each have many pages and I want to be as efficient as possible. You must have TracyDebugger. That is a requirement (should be in core ? ). It will save you many hundreds of hours of scratchin' your head. You may elect to use other modules, such as caching, etc. These are just the minimum I would recommend for a project like yours. I hope this helps.
- 5 replies
-
- 4
-
-
- classifieds
- subscriber
- (and 3 more)
-
Do you want this functionality available from the front-end or only from the admin side?
- 5 replies
-
- 1
-
-
- classifieds
- subscriber
- (and 3 more)
-
Hi @stemalo and welcome to the forums. You don't provide any details about your setup so I can only give you a general search, "site:processwire.com/talk super user has never logged in". This returns quite a few results regarding this topic. Maybe you can post your results when you find the one that solves your issue.
-
Hi @adrian, I've been cleanin' up my latest project and noticed this warning: Cookie “tracyClearDumpsRecorderItems” will be soon rejected because it has the “sameSite” attribute set to “none” or an invalid value, without the “secure” attribute. To know more about the “sameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Cookies I don't know if it means anything. If so, great. If not, please ignore this post. ?
-
Hello @hellerdruck (Roli) and welcome to the forum. This sounds like a standard distributorship application, which ProcessWire is more than able to handle. As bernhard said, it will depend upon your skills, whether you want to approach your task from a 'front-end' or from the admin interface. Jump in with any specific questions, and a whole bunch of knowledgeable PW developers will be glad to assist you.
-
Wow! I'm blown away with Processwire, incredible!
rick replied to Greg Lumley's topic in General Support
Welcome to the forum @Greg Lumley! Another great aspect of Processwire vs any other is this forum itself. You have access to many great developers that have been using PW for many years and their depth of knowledge will benefit you with whatever you want to create. So jump right in with any questions! -
The only thing I know about hooks is to catch fish. ? You might take a look at @kixe's module color field to see how it was done there. Another option, if you have a limited selection is to use individual pages for each color.
-
[SOLVED?] $pages->uncacheAll() doesn't seem to be working.
rick replied to elabx's topic in General Support
I am not familiar with AWS, but I am going to be using it with an upcoming project. My hesitation is based on other users having resource usage climb to higher price points based on AWS metrics. Meaning that AWS escalates usage parameters to move users into higher price brackets. It is only hearsay, so I don't have personal experience. @elabx, Do you think this is the case with your setup? -
Thanks for the links. I haven't looked into sockets in quite some time, but I do have an upcoming project to use this with. Thank you!
-
Except it requires composer to install. ?
