adrian

I just added several new links to Adminer from the Request Info panel. That Adminer icon links directly to this: These links have been added to the following Request Info sections: Page Info Module Settings Template Settings Template Info Field Settings Obviously be very careful editing content directly in the database like this - it's certainly possible to do critical damage!

Probably ? - that would be a Github issue/request for Ryan if you're keen!

That's because ProcessTracyAdminer is included as Part of TracyDebugger. This is a normal response for any included "helper" module in ProcessWire. Personally I don't like this behavior, but it is as expected. ProcessTracyAdminer will be automatically updated when you update TracyDebugger.

A couple of new features worth mentioning: 1) The RequestInfo panel's Field List & Values section now has a new "Adminer" column with a link to open the row for chosen field for the current page directly in Adminer. 2) I have finally committed the autocompletions for PW methods, properties and $page fields for the Console and File Editor panels. Hopefully you'll find this a nice shortcut, but more importantly a learning experience by finding new methods you didn't know about (or forgot).

Thanks @Robin S - really appreciate the quick fix. I actually have ~5000 siblings and it still seems to be working ok.

Hey @Robin S - looks like there is a bug when you're editing an unpublished page - it ends up messing up the $start value for the siblings selector so I end up with a list of pages that are nowhere near the page I am editing. Let me know if you can't reproduce and I'll see if I can figure out the problem later.

@kongondo - glad you sorted it out ? and good to know that docker appears to be a production server to Tracy. Just out of curiosity - do you usually use d($var) in template files? I always use bd($var). The only place d($var) makes sense to me is in the Console panel. Maybe you have a different use case or preference, or something else, but thought I'd mention it just in case.

Nothing is future-proof, not WordPress, not ProcessWire and not even PHP. If it wasn't for ProcessWire I probably wouldn't even be working in PHP anymore, but for now I find PW the most flexible, versatile and most fun tool to work with. While I would like more recognition and user base for PW, a lack of it is not going to stop it being my tool of choice. If clients trust me, they will accept my recommendations. I continue to refuse jobs where the client only wants WP - it's just not worth the hassle during development, security issues, and updates. To each his/her own though - if WP floats your boat then by all means use it - it's huge userbase, number of plugins, and developers familiar with it is both a blessing and a curse. For me I'd rather be part of helping to build something unique in the CMS space and the reason I built my own custom CMS's for each project for so many years - it's the ultimate flexibility of PW that drew me to it in the first place.

I've modified that first post with a new update to link here. Let me know if you'd like anything changed.

@Robin S - I went ahead and added the pluralize.js library. I have also added a check so that if the parent and child templates are the same, then the child template name is removed so that the form won't submit and you need to manually set them. A simple example to test this is using "Sheep" for the Field Label. In this situation I would just manually name the parent template to "sheeps" and be happy with that, but I didn't want to assume anything, hence the approach I took. Let me know what you think.

A couple of small updates to the Adminer panel / process module. 1) It is now restricted to the database for the PW install. Previously you could access all databases available with to the PW DB user. If some of you out there don't like this change, let me know and I can make it optional, but I think it's a better default (cleaner and a little safer). 2) It's now possible to uninstall the Adminer process module and it won't be automatically re-installed each time you upgrade Tracy - @Rudy was concerned about this with his setups. Obviously if a user has superuser access they can still install if they want, so it's more a case of removing something tempting for users without sufficient skills, rather than being a true change to security. On this note - Adminer is restricted to superusers (same with the Console, Snippet Runner and File Editor panels).

Hi Robin, I don't actually ever use the "_items" suffix myself - I always go with "cars" and "car" for the parent and child templates, respectively. That approach was to make things as logical as possible without the user having to change these settings. I am definitely keen to take a different approach though and the pluralize library seems like a good option. I see that it contains lots of rules for non-standard "s" suffixes, although it doesn't look like there any non-English ones provided. The other concern I have is the "Singular words with no plurals" list (https://github.com/blakeembrey/pluralize/blob/298eb67f19369dd30207c0817eda4f0045c6c1a7/pluralize.js#L393) - won't these result in the parent and child templates having the same name? Do we just need a check to make sure they're not the same and if so empty the child temptate name field and prevent the form from submitting until it is completed? Any thoughts?

Great - thanks for testing. I just committed another minor update that renames and reorders some of the settings and divides them into "required" and "optional" to make things a little more logical and quicker to complete.

Is this what you are looking for? https://processwire.com/blog/posts/processwire-core-updates-2.5.14/#multiple-copies-of-the-same-module This is what @arjen is referring to above. That said, I still think a hook approach is better if you can.

Done - let me know how it goes for you. I also fixed some other PHP7 issues with the Option 2 approach.

Hi @Robin S - I have fixed the bug regarding child page creation - I think it was a change to "empty" in PHP 7 that was the cause. I'm in transit now, but I can take a look at the new option for being able to set the parent page title in the next few days.

Actually please try a couple of versions back also. I'll certainly get this fixed when I'm back on the 12th, but it would be good to have things working for you before then. Also if you want to submit a PR for your feature request above is be happy to accept it. Perhaps discuss a little with @Jonathan Lahijani because I know he is planning some new features also.

@Robin S - would you mind checking the previous version? Not sure whether something new in this module might have broken it or possibly a change in PW.

Thanks @Robin S PR merged and modules directory updated.

@bernhard - there is a name () method from Adminer which I think will handle this. Only catch might be not wanting it in the panel version?

@Robin S - I wonder if a simple temporary solution might be to turn off error reporting at the top of the Adminer process module file?

Thanks for the PR. Maybe we need to get those plugins cleaned up. I'll take a look when I can unless you beat me to it☺

PS - I'll take a look at the possibility of custom compiling when I'm back. Also do you have any ideas on how to get around the debug mode issue?

Thanks everyone for the debugging. Would someone (maybe @Robin S) mind putting together a PR with his suggested fix for the &db issue and if you wouldn't mind also @matjazp's request for a custom port. I can easily merge a PR on my phone but not keen on coding ☺

I'm on the road now so can't help much but interesting @bernhard isn't having issues. Also weird that the file is referencing itself regarding the headers sent stuff. That said I can't see it being a core Adminer issue either. Hopefully you guys can help to figure it out for me ?