Ivan Gretsky

Good day! This module is in such a rapid development bringing tons of new awesomeness I just can't keep the pace even reading this thread . After upgrade (from a rather old version) the frontend panel stopped working for non-superusers. I figured out I need to create tracy-debugger permission and assign it to every role I want to test the site with. And probably remove the assignment on a live site (maybe only if it is in DEVELOPMENT mode). I often debug under different roles. Is the way described above the right one for it? Or there are some shortcuts? Maybe I am missing something obvious?

Sounds so good! And I just want to add my voice to @tpr's proposal made in the comments to one of the previous blog posts to integrate the best of the AOS features in to the core universal admin theme. So we can then just style them or turn them on and off like in the mentioned module. Maybe we can not only bring some new look but improve functionality at the same time.

I want to thank you Ryan for organizing this community effort. Inviting and encouraging to participate in development, making it this straight forward is something rare and yet unusual even for such a great community as ours. It is interesting how things will turn out. Seems like @renobird is going to be leading this endeavour. What could be our strategies to participate? P.S. By the way, do not forget to check out the off-canvas menu in the demo.

I guess writing comment is much more enjoyable in the forums, but not in the code) For now I settled on this syntax for non-phpdoc multiline comments. Without any particular rules on where to write them. /* * Comments here. */

I have not. Just wanted to share this option to install to AWS. Maybe not what you were looking for, but still an option.

Good day! I do not know what exactly is happening, just trying to move the topic forward. Please provide more details. I understood that you got a ckeditor.js failed to load message in your browser console on some non-admin url of your site when trying to open a front-end editing popup. Is that right? Please provide more details/context/screenshots to make it easier to answer. Seems to be PW unrelated problem. Did you check some ckeditor related answers? I know, it's close to "go google it", but that is how I would start.

I was thinking of a few endpoints to handle authentication with the template permissions. One for the public, another for the registered users with the ability to make changes via mutations when they'll be implemented. There are other ways to handle authentication of course. But then we will have to implement some restrictions via module itself. But maybe I am not seeing something obvious here.

Here is another idea. What about the ability to make a number of API endpoints with different allowed templates and restrictions based on single instance of a module. By passing an argument to executeGraphQL() or something like that. With the ability do distinguish them in hooks. A way to have a public and less public API on the same site. I guess than some authentication questions could be solved on a template level.

Thank you very much for this module, @Nurguly Ashyrov! I missed this graphql thing completely, though was messing around json api a bit. Had some great time reading about it. Seems like ProcessWire fits graphql like a glove. Your module should answer a lot of recent questions about integrating PW with vue.js and alike. Dries Buytaert, the Drupal "godfather", has a nice article in his blog about the necessity for a contemporary CMS to have support for web-services built in. And his choice seems to be graphql and json api. I am sure that improving and promoting PW as a "headless CMS" kind of thing is something that could bring a lot of frontend developers to use PW. This module is the perfect start. As I understand, mutations are a way to not only read, but write data? If so, that is certainly worth implementing, so a complete SPA could be possible with this graphql module alone.

Good day! Looking at @ryan's wonderful documentation I am trying to document my code better. Of course the main standard is phpdoc. I think that is what is mostly used in PW core code and almost everywhere in php world. But phpdoc only standardizes commenting only some elements, like variable definitions, classes, methods. As I write a lot of procedural code in template files I need to document code parts which are not supposed to have their DocBlocks by phpdoc standard. So I am looking for recommendations/standards how to write those. I guess there should be some distinction between simple multiline comments and phdoc DocBlocks. Maybe something to consider about IDE integration or something like that. What I found so far is these (seemingly) phpdoc non-compliant comments in new skyscraper profiles, and these Wordpress recomendations. If you got any thought and/or links on the topic, please share!

Thanks. I think I got it all right, as the pagination actually works, and the pager does display/ But it is the same on every paginated page. I implemented pagination several times, so there is either a typo or some stupid error in the code I just could not find going through code a million times, or some limitation/bug I do not know about.

Service types will be almost the same under each company. So to keep it DRY I would not place this in a tree structure. Plus you need the ability to make api calls for filter functionality - Page Field will probably be better for it. Tree structure seems to be easier for admin management (unless you plan to use Lister Pro module). So I can propose doing it in a mix: put plans under company, make a service type Page Field for plan.

Good day! Suddenly I stumbled upon pagination once again. Pagination itself works as expected, but renderPager() returns the same markup on every paginated page. So it is 1st page current on every /pageN/. What can cause this? Please help.

There is continuation of this discussion with some solutions on github. This seems to be the problem with locale settings.

Thanks, @Robin S. I think kongondo's answer solves my issue. For now I do not seem to need the ability to check what permissions are added by the module. Thanks for the support.

Thank you @adrian! It is amazing to watch something being created with such an amazing pace by people like you and ryan. And so much to learn from. I recommend everybody to go through these guys' code to learn how you can be really powerful using ProcessWire. Another little idea. Not sure it is necessary, but seems logical to me to separate "core" actions and those specific to the site. Like core ans site modules. I can see this module to be a base to easily create little things that would other way need their own process modules. In that case, most of the time I would use only custom actions... A filter option or a tab. What do you think? I know, that for everybody but admin I can achieve about the same with by-action role assignment. But as I almost always login a superuser myself...

Good day! I have a hook addHookBefore('FieldtypeMulti::savePageField'... Inside that hook I need to create and save an additional page. If I add that code to the hook, on the original page save the changes to Page field do not get saved. All other fields do. If I change hook to After the problem goes away. But I have so much code now I do not know if it is safe to change hook to run after the method. If anyone has any guesses, why is it like that and how to fix it, please help!

Just to have a reference. There is a native PW way to generate random string. Do not know how it compares to other ways, but it is here to use.

Thank you for your best-in-class support.

I did already managed to write a simple action and launch it via the API. I am currently going with a json in a textarea (but also looking at this field). Mandatory backup is problem 1. I had to give admin-action permission to the guest user. Not sure how dangerous is that. Is there a way to get around it? I am planning to have some security string stored in a dedicated field on the callable-from-outside action page which the token input value will have to match. Is there anything else you recommend? Not sure what you mean under handling authentication. Currently the script is running from the guest user.

Merry Christmas, @adrian! Want to try to use your action module in a slightly different way. I need to be able to execute actions from outside of PW (from emails). I am planning to solve this task kind of like in this module: I will have a page for each callable-from-outside action with some random security string and some options. But I want to try to make it a little more customizable. I plan to write new actions for Admin Actions module, call them from API like you said it is possible to and pass options stored in some field of the callable-from-outside action page. Do you see any caveats? Can you suggest a field to store options? Is there a way to turn off auto-backup feature (at least for the from-API usage or by configuration)?

Hi @Robin S! Wonderful module! What is the API way of checking, which templates are allowed for the page?

Nice catch! See it too. I guess that is Putin's personal hacker squad making itself known to all web-traffic concerned .

@workdreamer There is a way to override core modules, but it is certainly not the best way to handle the situation here in my opinion. But still an option. And welcome to the forums, man! You've found a thing to work on you could only dream of!