adrian

Sorry to hear about these issues - I'm not really sure what to suggest at the moment. If you see them again, could you possibly dig a little deeper to see if there is something in Tracy that needs fixing?

Thanks for your research and thoughts @Robin S - much appreciated as always, but I wonder about the "near miss" you are suggesting. Given that files under /site/modules/ can't be executed directly and I have Adminer locked down to superusers only, I am wondering how that version with the vulnerability could have been exploited within a PW system? I know that nothing is ever completely secure, but wouldn't it take someone with filesystem access to be able to do any damage in this case, and if they have that, then there are lots of other ways they could do damage anyway. Am I missing something? I'm definitely happy to hear more arguments for (or just more folks in favor of) separating it into its own module.

Thanks for your hard work in getting lots of stuff resolved Ryan! Any chance you could prioritize this one: https://github.com/processwire/processwire-issues/issues/1116 It seems very critical to me for any site that uses URL segments and the link abstraction feature in CkEditor fields. Thanks!

@teppo - certainly not a bad idea. It's actually what I did with the Terminal panel for the same reason. However, this is the first report I've had of Adminer being flagged as spam by a host, so I might wait to see if others also have the same issue. I am hesitant because I think this is a such a useful panel - I use it many times a day - I really love the context sensitive initial view it gives depending on what you are currently viewing / editing in the admin. As well as being a great utility for getting things done, I also think it's a great learning tool for users new to PW so I'd hate to make it harder to find for new users.

Hi @kp52 - thanks for the report. Not really sure what to do - Adminer isn't spam, but I understand that hosts see it as something that can be used maliciously. In the case of this module, it's not possible to load it without being a logged in superuser - apache htaccess restrictions prevent direct access to the file.

Just to clarify, in case you don't know, having a template name with an underscore doesn't at all impact the URL of pages using that template? That said, I've gone ahead and added an option to choose from an underscore or dash for the template names. Please grab the latest version.

@bernhard - I've been using the feature built into AOS for this. You can see the code for it here: https://github.com/rolandtoth/AdminOnSteroids/blob/2e8f9c56dbc0d05edcb203d7dcf9af31eb862b02/AdminOnSteroids.module#L780-L796

https://processwire.com/docs/front-end/markup-pager-nav/

@michelangelo - the non-pro version of the Lister doesn't support inline editing. If you don't want to buy ListerPro, then you could perhaps modify the normal BCE edit mode to support custom fields (that wouldn't be too hard actually). The more complicated part would be building in the pagination, which BCE doesn't currently have, although it really does need it, especially with your setup with 3346 child pages. I don't really have time to work on adding those things any time soon, but they would make great additions if someone wants to contribute via a PR.

I moved a couple of production servers to 8 about 2 weeks ago. Everything looks good so far. The only bug I found was in my own code related to 0 vs ''

Bit me once again today :) In this case I did have that module installed, but even after disabling it, I still had issues with a particular template where I had specifically set noLang in the advanced template settings, so watch out for that.

I added this to my search.php template file. Hope that helps. $searchEngine->addHookAfter('Renderer::renderResult', function($event) { $p = $event->arguments[0]; $image = $p->getunFormatted('pdf_images|image|images|video_images')->first(); if($image) { $thumb = $image->size(0, 260, array('upscaling' => false)); $event->return = ' <div class="row"> <div class="small-12 medium-4 large-5 xlarge-4 xxlarge-3 columns teaser__image"> <a href="'.$p->url.'"> <img style="max-height: 300px" src = "'.$thumb->url.'" /> </a> </div> <div class="small-12 medium-8 large-7 xlarge-8 xxlarge-9 columns teaser__content"> ' . $event->return . ' </div>'; } });

Sorry about that - looks like I messed up the property name. I just tested though with "roles" and it's working here, eg: $options = array( "page_protected" => true, "children_protected" => true, "roles" => array("editor"), "message_override" => "My custom login message", "prohibited_message" => "My custom prohibited access message" ); $page->protect($options); I'll fix the documentation in a minute, but you you please try the above to confirm it's working for you.

@Macrura - thanks to @Robin S in another post: https://processwire.com/talk/topic/15902-hannacodedialog/?do=findComment&comment=208498 // add hanna code dialog to fields even though the Hanna code text formatter isn't applied // https://processwire.com/talk/topic/15902-hannacodedialog/?do=findComment&comment=208498 $this->wire()->addHookAfter('InputfieldCKEditor::renderReadyHook', function (HookEvent $event) { $inputfield = $event->object; $field = $inputfield->hasField; // For your field name(s)... if(!$field || $field->name !== 'XXXX') return; $config_name = "InputfieldCKEditor_{$field->name}"; $config_name_matrix = "InputfieldCKEditor_{$field->name}_matrix"; $config = $this->wire('config'); $js_config = $config->js(); foreach($js_config as $key => $value) { if($key === $config_name || strpos($key, $config_name_matrix) === 0) { $js_config[$key]['extraPlugins'] .= ',hannadropdown,hannadialog'; $config->js($key, $js_config[$key]); } } });

Ah sorry, the way I read things, I thought he had already fixed the separator issue and still didn't like the column widths.

CSVs don't have widths. You are using Excel to view a CSV. If you want a properly formatted Excel file, it's pretty trivial to write an API script to export a series of pages to an Excel file with something like https://github.com/PHPOffice/PhpSpreadsheet which lets you format the spreadsheet almost however you want.

BCE comes with a comma in that option by default ?

@pwfans - I wonder, do you have a copy of ListerPro? This might be a better option for your needs. It's inline editing isn't quite as convenient as BCE's, but it has pagination and searching and so it scales infinitely.

But how nice would that interface actually be for hundreds / thousands of pages? What sort of bulk edit actions are you referring to? Changing status, or deleting etc? I suppose there could be a way to select all across all pages if they were to be paginated. I'm afraid I just don't see it as the right tool for the job in this case, but if you want to add support for this, I'm happy to accept a PR.

@donatas - the only viable approach is to use teppo's add-on module: https://processwire.com/modules/admin-restrict-branch-select/ Any other approach would be a complete rewrite and would have other complications.

@pwfans - I always disable BCE for pages that have too many children for the edit mode to handle. I don't really think the edit mode makes much sense with that many pages anyway so I don't think pagination will help. If you need to batch edit that many child pages you probably need to write a script via the API (Tracy Console panel or AdminActions perhaps?) to make the changes.

There is also https://processwire.com/store/pro-dev-tools/user-activity/ so given that, I don't see anything like it ending up in the core.

@ryan - what about a dedicated "Skins" section - maybe within the modules directory. Perhaps the requirement for adding a skin to the directory would be to link to a Github repo with the admin.less and also an admin.png file which could be used on the skin's page in the directory. Ideally I think it would be nice if it was possible to view all skin screenshots via a gallery of thumbnails to make it easy to browse visually.

@Tom - I think the field=title within the quotes selector, vs having the list of fields in a separate quoted group is optional either way. The "array_values" is needed because the text tags needs the array to be indexed numerically starting at zero, rather than the page IDs which findRaw() returns.

@Pete - I'd like to second this - is it an easy fix to show the full message in the email? Thanks!