Leaderboard

Released 0.2.0 + 0.2.1 Theme is now a module extending AdminThemeUikit by replacing the CSS This simplifies the installation, simply download the module and install it Added extended breadcrumb with edit links Added option to activate the theme for all users Updated look of checkboxes and radios – thanks @flydev for inspiration Release 0.2.1; Styled login form

Hey @openmedi. Welcome to the support forum! I'd start by looking into the WireShell "new" command, which is documented. Haven't used this myself, but it seems like it should do exactly what you need.

Admin Theme Boss A light and clear theme based on Uikit 3 Features Five unique color options Beautifully redesigned login screens Modern typography using Roboto Condensed Extended breadcrumb with edit links Extends AdminThemeUikit, so you can continue using all current and future AdminThemeUikit features Option to activate theme for all users Compatibility with AdminOnStreoids and other third party modules Updated and Releases There is a shiny new release page where you can subscribe to updates for new releases of AdminThemeBoss. Color Variants: ProcessWire Blue Dark Black Vibrant Blue Happy Pink Smooth Green *new with 0.6.1* Requirements Requires a current ProcessWire version with AdminThemeUikit installed and activated. Installation Make sure AdminThemeUikit is activated Go to “Modules > Site > Add New“ Paste the Module Class Name “AdminThemeBoss“ into the field “Add Module From Directory“ Click “Download And Install“ On the overview, click “Download And Install“ again… On the following screen, click “Install Now“ Manual Installation Make sure the above requirements are met Download the theme files from GitHub or the ProcessWire Modules Repository. Copy all of the files for this module into /site/modules/AdminThemeBoss/ Go to “Modules > Refresh” in your admin Click “Install“ on the “AdminThemeBoss“ Module

Post them on here if you want @bernhard I don't mind having a crack at fixing them ?

Hey, I've been working with UIKit for about 4-5 years now. There are a few IE11 bugs relating to flex box. I would try changing your markup from: <div class="uk-child-width-1-1 uk-child-width-expand@m uk-child-width-1-2@s uk-flex-center uk-grid" uk-grid=""> <div class="uk-flex uk-flex-center uk-flex-middle uk-first-column"> <div> <div class="uk-inline "> <img data-src="/site/assets/files/1262/imageedit_5_5811401713.600x400.jpg" width="" height="" alt="" uk-img="" src="https://www.hrdiamonds.com/site/assets/files/1262/imageedit_5_5811401713.600x400.jpg"> </div> </div> </div> <div> <p style="text-align:justify;"><strong>Qualität - Begeisterung</strong><br> Wir setzen neue Maßstäbe mit unseren lösungsorientierten und umsetzungsstarken Konzepten. Vor Ort begleiten wir Sie bei der erfolgreichen Durchführung der gemeinsam beschlossenen Maßnahmen. Wir begeistern Sie mit unseren Ideen und unserer engagierten Arbeitsweise.</p> </div> <div class="uk-flex uk-flex-center uk-flex-middle "> <div> <div class="uk-inline "> <img data-src="/site/assets/files/1264/imageedit_2_9167790703.600x400.jpg" width="" height="" alt="" uk-img="" src="https://www.hrdiamonds.com/site/assets/files/1264/imageedit_2_9167790703.600x400.jpg"> </div> </div> </div> <div> <p style="text-align:justify;"><strong>KundIn - Familie</strong><br> Wir gestalten mit Ihnen eine individuelle und persönliche Arbeitsatmosphäre. Sie als KundIn sind Dreh- und Angelpunkt und stehen im Zentrum unserer Aufmerksamkeit. Trotzdem wollen wir eine Balance zwischen Beruf und Familie schaffen – für Sie und für uns.</p> </div> </div> To: <div class="uk-flex-middle uk-child-width-1-1 uk-child-width-1-2@s uk-child-width-1-4@m" uk-grid> <div> <img data-src="/site/assets/files/1262/imageedit_5_5811401713.600x400.jpg" uk-img> </div> <div> <p style="text-align:justify;"><strong>Qualität - Begeisterung</strong><br> Wir setzen neue Maßstäbe mit unseren lösungsorientierten und umsetzungsstarken Konzepten. Vor Ort begleiten wir Sie bei der erfolgreichen Durchführung der gemeinsam beschlossenen Maßnahmen. Wir begeistern Sie mit unseren Ideen und unserer engagierten Arbeitsweise.</p> </div> <div> <img data-src="/site/assets/files/1264/imageedit_2_9167790703.600x400.jpg" uk-img> </div> <div> <p style="text-align:justify;"><strong>KundIn - Familie</strong><br> Wir gestalten mit Ihnen eine individuelle und persönliche Arbeitsatmosphäre. Sie als KundIn sind Dreh- und Angelpunkt und stehen im Zentrum unserer Aufmerksamkeit. Trotzdem wollen wir eine Balance zwischen Beruf und Familie schaffen – für Sie und für uns.</p> </div> </div>

OMG, not again... https://www.pilcro.com/blog/headless-cms By that definition, PW is most definitely a HCMS...

Great work! I prefer the default uikit theme but just gave it a try and everything worked. Here's a kickstartfile if you want to use PW Kickstart to try it out quickly using PW Kickstart:

In this demo video, it is working from the existing 'home' template. All Ajax requests are going directly to the existing ProcessPageEdit url. there are no 'dynamic templates', but very shortly, you will have the ability to create templates on the fly from the page tree and start editing directly in Designme to speedup template/data model creation. So you can start with a completely blank template/editscreen and start throwing in fields as fast as possible. (hope this makes sense).

LogMaintenance A simple ProcessWire module to give some maintenance control over log files. I found myself often having lots of log files for different things that can grow more or less quickly to a size where they can be difficult to maintain. The built in Logger of PW does a good job of giving you the possibility to delete or prune logs. But it has to be done manually and sometimes a log grows into millions of lines, which makes it often impossible to even prune it as it's too large. LogMaintenance uses LazyCron to run the maintenance task and there's several settings you can setup on a global or per log basis. Archive: will create zip files for each log file in logs/archive/ folder and add the log each time the maintenance is run to a subfolder containing the datetime. Lines: keeps logs to a certain number of lines Days: keeps the log to a certain number of days Bytes: keeps the log to a certain amount of bytes Each setting is checked from top down, the first setting to contain something is used. So if you check the "Archive" option, all other settings are ignored and logs are archived everytime the LazyCron is executed. If you want to keep your logs to a certain amount of bytes just leave all other settings to 0 or blank. Per Log Settings There's a textarea that you can use to setup a config for a specific log file one per line. All the logs you define here ignore the global settings above. The syntax for the settings is: logname:[archive]:[lines]:[days]:[bytes] errors:1:0:0:0 // would archive the errors log messages:0:10000:0:0 // will prune the errors log to 10000 lines The module can be found on github for you to check out. It's still fresh and I'm currently testing. https://github.com/somatonic/LogMaintenance

wireshell new --profile=blank Your new best friend! ?

@Noel Boss thanks for this module. Installed without a problem. Guess it's not yet in the modules directory? What I don't get is what is Extended Breadcrumbs for? The theme is almost 18 MB in size, seems a lot for a few css files? Just for fun, I took uikit.vibrant.css file and used it in AdminThemeDefault config options (Layout + interface, Advanced) and got the look and feel without using your module. Or I miss something?

@teppo Thanks for pointing that out! This is probably exactly what I was looking for! I guess I got confused by the background colors. I guess that's because this is supposed to be a display of hierarchy, which was not immediately apparent to me, instead I assumed there were only three commands available to me.

Thanks for your help @jmartsch ! I renamed all references to FieldtypeRockGrid, so it should work now without renaming the folder. Thanks for that hint! Maybe someone wants to create a PR for the problem of installations inside a subfolder - I don't have any need for that and therefore will not implement it. At least not soon. I created a screencast of a demo installation via PW Kickstart, the Kickstartfile is here: https://gitlab.com/snippets/1732038 ; Of course you can also install everything manually.

Do you know Processwire Kickstart ? ?

@netcarver your version fixes the conflict in my installation. Thank you !

Hi @bernhard I tried to test and reproduce why this isn't working. When you install RockGrid and RockFinder from URL from Gitlab, then the RockGrid is downloaded and installed into a folder named "FieldtypeRockGrid". But RockFinder tries to look for files in a folder named "RockGrid". So Rockfinder tester isn't working and shows the error that I described and @mel47 also described. That's the first problem. You can solve it, if you download the zip file from gitlab, unzip it in your site/modules folder and remove the "-master" from the folder name, so the name of the folder is "RockGrid". The second problem is, that if your processwire installation is not in the root of the virtual host of Apache (for example in a subdirectory), then the URLs for loading RockGrid's assets isn't correct because it tries to load the files from the root and does not take the subdirectory into account. In one example installation I have two separate PW installations under the same virtual host but in different subdirectories (mydomain.localhost/pw1, mydomain.localhost/pw2). That might be the exact same problem that @mel47 has. If you open RockTester then it is trying to load http://mydomain.localhost/site/modules/RockGrid/plugins/cellHoverInfo.css instead of http://mydomain.localhost/pw1/site/modules/RockGrid/plugins/cellHoverInfo.css

If you have a lot of fields on the page/template in question it would be worth increasing max_input_vars to see if that solves it. https://www.virendrachandak.com/techtalk/big-forms-and-php-max_input_vars/

https://www.cockos.com/licecap/

Quick update... my site already had a service worker registration file, PWABuilder. Each site can only have one service worker registration. With PushAlert's help, I managed to overcome this issue. Their software dictates that they register the service worker with a predefined file name, sw.js. Politely suggested they rethink this approach as other sites will have their own service worker registration files and who knows what problems may ensue if all vendors insist on their app registering the service worker? Awaiting outcome of that recommendation. Next, using the PushAlert cURL code, got notifications working on FF & Chrome. Haven't ventured into Safari territory yet as it involves a whole lot of baloney with Apple certificates. Sending notifications works well providing you don't mind getting double notifications when PWABuilder is installed with page cache/offline configured. Sigh... Plan is to continue development of PW integration with PushAlerts and, until service worker fluff is resolved, offer clients either push notification OR offline/fast page load. Will also do best to make calls to PushAlerts using WireHttp instead of their cURL code. Stay tuned!

Ok, the culprit was that CKE needs some time on startup to dynamically create the iframes. Therefore all those tries running on document load failed. As a workaround I use setTimeout() with a delay of 1000 ms to start finding the iframes. Will look into CKE API, if there is something that can be queried that indicates ready loaded CKE and use this instead of my workaround. But for today I'm finished with work. ?

@Jules Vau Yes, thats correct. The setting in site/config.php overwrites the one in the wire directory.

It's all there. When I was starting with PW years ago, I very soon looked at modules and all the Process modules that make the admin. So I never really needed a tutorial, just look and learn copy and try. It was so simple and since it's all in the same fashion using the already familiar API and "normal" modules. So you have a ton of modules Ryan has already built that make ProcessWIre backend you can use as examples/learning. Isn't it nice?

Nice job @Noel Boss ! Already adopted, modified & installed ! I just tweaked it to get a Google look (controls), removed the transparency on dropdown and reversed the fonts and notes.

Thats not practical since the "overrides" would need to be at so many places. With Uikit you've got LESS where you inject your colors etc. at various places. You replace code, not just override it. Simple overrides would be much more complicated and and could potentially break on an updated base theme. Replacing the whole CSS makes sence. BUT, you're suggestion just triggered an idea: Publish it as a propper Module and replace the CSS of the AdminThemeUikit with a hook… This way, AdminThemeUikit would still be technically the Theme, but the CSS (and potentially JS) would be entierly replaced by the "Child" Theme. In this way, one would also not need to change Settings etc… Brilliant! But I think, the required Method is not (yet) hookable… I guess it is hookable, since it's public…

Yes, I think the module should do this (or offer an option for it). Because the name field is normally on the Settings tab, and if you are removing that tab for a role then you probably don't want the role seeing any of the fields normally on that tab. You probably know this but it was new to me... you can add styles to an inputfield without needing to include a CSS file with the module: $if = $wrapper->getChildByName('_pw_page_name'); $if->wrapAttr('style', 'display:none;');

I'm trying to replace default templates for "templates" CKEditor plugin (in site folder) without any luck. My installation runs templates.js from "dialogs" folder (from wire folder). I have seen others have same problem: Please, help. Nikolay Antoshenkov P.S. Just have found solution: Added line config.templates_files= ['/site/modules/InputfieldCKEditor/plugins/templates/default.js']; to config.js

If you do not assign a title the autogenerated ID (Inputfield) will be taken. $inputfields->attr('title', 'Weird name'); To put the Inputfields (Tabs) in the right order you could use InputfieldWrapper::insertBefore() or InputfieldWrapper::insertAfter() instead of InputfieldWrapper::add(). Unfortunately this doesn't work in case of ProcessPageEdit. To get it working you need to add another hook to ProcessPageEdit::getTabs() The following code snippet should work. Place it in your /site/ready.php wire()->addHookAfter('ProcessPageEdit::buildForm', function ($event) { $page = $event->object->getPage(); if ($page->template == "bewerbung") { $form = $event->return; $inputfields = new InputfieldWrapper(); $inputfields->attr('title', 'Weird Name'); $inputfields->attr('name+id', 'WeirdTabNameAndId'); // we need both unique ID and Name $markup = wire()->modules->get('InputfieldMarkup'); $markup->label = 'Custom Lable'; $markup->value = '<p>Just a placeholder for any custom markup</p>'; $inputfields->add($markup); $pageEditTab = $form->find('id=ProcessPageEditContent')->first(); $form->insertAfter($inputfields, $pageEditTab); // inserting in the right place is not enough to set the tab order // we need the following hook wire()->addHookAfter('ProcessPageEdit::getTabs', function ($event) { $event->return = array_merge( array_slice($event->return, 0, 1, true), array('WeirdTabNameAndId' => __('Weird Name')), // should be identical to the weird name/title above array_slice($event->return, 1, null, true) ); }); $event->return = $form; } });

This happens when the user PHP runs as isn't the owner of the cache files. The file compiler tries to update the cache files with the modification time of their originals, and while writing to that file can succeed through group permissions, updating the modification time fails unless issued by the owner. Clearing the cache removes the cache files and recreates them with the PHP user as the owner, so the problem is gone.

We discovered a similar problems while debugging our page using Chrome Developer Tools. When you enter the mobile inspector, your user agent changes. If you then happen to use the ProcessWire Backend WITHOUT the mobile inspector, you'll get logged out. I followed the session tracelog and noticed that the fingerprint changed and thats why I got logged out. The fingerprint is dynamically created using a md5 hash with the request user agent & request_ip. Since the user agent changes in mobile inspector, your session fingerprint will be different and therefore processwire logs you out. Took me while to figure this out. Hope this helps others.

I can set the user timezone with date_default_timezone_set. It is important to set it before my form gets rendered, submitted and processed, not just before I save values. The current time in my date field gets calculated based on the set time zone. Example: set timezone Europe/Berlin, current date set timezone America/New_York, current date When PW saves publishing timestamps, I get timestamps for 2014-10-24 03:00 Europe/Berlin: 1414112400 America/New_York: 1414134000 Which is 21600 seconds or 6 hours off. Which is correct. So I think I'm on the right track now handling different timezones.