Leaderboard

Just my 2 cents, but I'd rather see just the one official admin theme that supports top and side menus. The key thing is that I'd like to have that official theme easily skinnable. I would love the options to color and style the theme with CSS while keeping all the html and php standard. The problem with some of the third party themes back in the early PW 2 days was that new features added to the default theme never made it to the third party themes. I'd also love to see the page tree in the sidebar and the other menu items (setup, modules, access) in the top menu. I am not certain, but I think now that the page tree is cached it won't be a performance issue to have it in the sidebar anymore?

I'll be reworking the Reno Admin theme to take advantage of UIKit and all the refactoring Ryan is doing.

May I ask why? The readme says: "Obtain a fresh copy of ProcessWire 3.0.51 or newer"

Hey Kongondo, I think 3rd-party admin themes will be even easier than before. What I meant was that since Reno is kind of a core theme, it doesn't make sense to develop it separately *if* — and it's still a giant *if*— the new default theme allows you to configure a setup that is basically the same as the current Reno theme. We are deeply invested in the Reno theme here, so either the new admin will be customizable to something very similar, or I'll keep developing Reno as separate theme. I have some things I'd like to implement that UIKit will make easier, and I'm excited to dive in once Ryan has a stable base theme to work from.

I've to agree with adrian. I'd also like to see api access to those theme colors, so if one does need to add custom styles in modules, they update with the theme settings.

@MarcU Your $item->thumbnail is probably not set, and thus a non-object (so you can't get its url without the Notice). Are you checking if your have an $item->thumbnail before trying to access it's property?

NOTE: This thread originally started in the Pub section of the forum. Since we moved it into the Plugin/Modules section I edited this post to meet the guidelines but also left the original content so that the replies can make sense. ProcessGraphQL ProcessGraphQL seamlessly integrates to your ProcessWire web app and allows you to serve the GraphQL api of your existing content. You don't need to apply changes to your content or it's structure. Just choose what you want to serve via GraphQL and your API is ready. Warning: The module supports PHP version >= 5.5 and ProcessWire version >= 3. Links: Zip Download Github Repo ScreenCast PW modules Page Please refer to the Readme to learn more about how to use the module. Original post starts here... Hi Everyone! I became very interested in this GraphQL thing lately and decided to learn a bit about it. And what is the better way of learning a new thing than making a ProcessWire module out of it! For those who are wondering what GraphQL is, in short, it is an alternative to REST. I couldn't find the thread but I remember that Ryan was not very happy with the REST and did not see much value in it. He offered his own AJAX API instead, but it doesn't seem to be supported much by him, and was never published to official modules directory. While ProcessWire's API is already amazing and allows you to quickly serve your content in any format with less than ten lines of code, I think it might be convenient to install a module and have JSON access to all of your content instantly. Especially this could be useful for developers that use ProcessWire as a framework instead of CMS. GraphQL is much more flexible than REST. In fact you can build queries in GraphQL with the same patterns you do with ProcessWire API. Ok, Ok. Enough talk. Here is what the module does after just installing it into skyscrapers profile. It supports filtering via ProcessWire selectors and complex fields like FieldtypeImage or FieldtypePage. See more demo here The module is ready to be used, but there are lots of things could be added to it. Like supporting any type of fields via third party modules, authentication, permissions on field level, optimization and so on. I would love to continue to develop it further if I would only know that there is an interest in it. It would be great to hear some feedback from you. I did not open a thread in modules section of the forum because I wanted to be sure there is interest in it first. You can install and learn about it more from it's repository. It should work with PHP >=5.5 and ProcessWire 3.x.x. The support for 2.x.x version is not planned yet. Please open an issue if you find bugs or you want some features added in issue tracker. Or you can share your experience with the module here in this thread.

Croppable Image 3 for PW 3.0.20+ Module Version 1.2.0 Sponsored by http://dreikon.de/, many thanks Timo & Niko! You can get it in the modules directory! Please refer to the readme on github for instructions. - + - + - + - + - + - + - + - + - + - NEWS - 2020/03/19 - + - + - + - + - + - + - + - + - + - There is a new Version in the pipe, that supports WebP too: - + - + - + - + - + - + - + - + - + - NEWS - 2020/03/19 - + - + - + - + - + - + - + - + - + - ------------------------------------------------------------------------- Updating from prior versions: Updating from Croppable Image 3 with versions prior to 1.1.7, please do this as a one time step: In the PW Admin, go to side -> modules -> new, use "install via ClassName" and use CroppableImage3 for the Module Class Name. This will update your existing CroppableImage3 module sub directory, even if it is called a new install. After that, the module will be recogniced by the PW updater module, what makes it a lot easier on further updates. ------------------------------------------------------------------------- For updating from the legacy Thumbnail / CropImage to CroppableImage3 read on here. -------------------------------------------------------------------------

This week we’ve started developing a new admin theme for ProcessWire that aims to be a community collaboration. We’ve now got some good momentum with lots to share in this post. We also get into some technical details and have screenshots as well. https://processwire.com/blog/posts/working-towards-a-new-admin-theme/

In the field settings... But better to solve this with CSS by adding some bottom margin to your images.

In my last couple of projects I've used a hacked version of this module with an extra field for inputting image map coordinates. With a little snooping around and a good dose of patience my lack of module building knowledge didn't stop me So now this shopping centre's website has a store locator where you can hover hotspots, the marker appears in place and everything is configurable in the CMS. Before this was a Swiffy converted flash object. Here's the result in the frontend: http://www.miramaiashopping.pt/lojas/ And here's what it looks like in the CMS: Now I do have another project where I also have to add hotspots to an image for showing some text. But for that the module needs some serious work. I'm just going to make subpages of a type that only has a body field and use that. It would be cool to have this work like a repeater where you have full control of the fields for each marker and only link to pages if you need to, but that would mean rebuilding from the ground up.

@adrian We have some that are 8-10 levels deep here, and then lengthy titles (you know, academics. ;P). I'm certain it's a useful feature, but I won't want that to be the primary way to interact with the page tree. Being able to access the pagetree from a panel that overlays pageEdit would seem sufficient to me, especially if it's keeping track of whatever state it's in.

I think we are talking about 2 things here. If the new default ends up covering everything that Reno does, then it will be obsolete and no longer developed. If not, we are really tied to using Reno here, so at first I'll be making sure it works (as-is).

Well in this case I (kinda) solved my issue using an array like this; $selector[] = ['field' => 'date_pub_end', 'operator' => '<=', 'value' => $now, 'not' => true]; I also read the documentation about the array-selectors in the blog and from Ryan but I guess we still have to wait a little bit for the upgraded documentation for this announcement; Tnx anyways @Macrura @kongondo for pointing me in the right direction!

<? ?> is removed in php 7.0 is only available with short_tags enabled in php, which it isn't by default, use <?= ?>, which are always available. See here: http://php.net/manual/de/language.basic-syntax.phptags.php

@Robin S I understand your concern, however this is default but will not remain default. What I get from this blog post is Ryan wants to work with the designers on this forum to customise UIKit using it's built in classes to create a front-end which will be ProcessWire's new default. I personally love the new simplistic approach and it's pretty much an empty canvas for us to inject some personality. For our website - http://peterandpaul.co.uk/ we use our own customised version of the backend.

AdminOnSteroids is nice and it's features should be evaluated for the new admin theme, but I'm not sure there's even remotely the need to implement them in the core like you're describing things. The core should not strive for feature completeness, but rather in the direction of the simplest possible subset of features needed by most of our users. Everything else is a matter for optional (core or 3rd party) modules. Talking about your example I'd imagine that hiding description/notes is rather a anti-pattern for most use-cases as they're usually filled with information the editors/moderators of a site tend to forget but are important none the less.

cool, in that case it should be easy, you just use that exact syntax, but add the 'group' key: $selector = array( array( 'field' => 'date_pub_end', 'operator' => '<=', 'value' => $now, ), array( 'field' => 'date_pub_end', 'operator' => '=' , 'value' => '', 'group' => 'foo' ), array( 'field' => 'date_pub_end', 'operator' => '>=', 'value' => $now, 'group' => 'foo' ), ); i theeenk

I am wondering if maybe it's a similar situation to this one? (i.e. it's not possible without some verbosity as ryan explains here in response to a filed issue).

If you have ever updated the PW version using the Upgrades module you probably will have created a DB backup then. Is there anything in /site/assets/backups/database/ ? For the future: http://modules.processwire.com/modules/cronjob-database-backup/

Not planning on it - just trying determine whether the post actually belongs in the PW forums or not

Only if it's executed before or after template rendering, which is most of the time, but not always. That's why I go with this in places, where I cannot be sure about the state of output formatting: $page->getUnformatted('image')->first()->url

Sanitization does not have much to do with queries per se. You sanitize user input not the query. And to answer the question about automatisms. When editing a page the fieldtypes of the fields add their own sanitisation based on how things are set up (see Fieldtype::sanitizeValue and child classes). Elsewhere there's nothing automatically sanitized.

Actually, output formatting is always off in a module. If output formatting is off, Image fields will always return an array, no matter your settings. So...first(), last(), eq()....are your go to guys...

It's not a bug - when saving, output formatting has to be off. PS - you should get familiar with Tracy: bd($page->of()) is a lot easier than messing around with ob_start and var_dump

Well, that's weird - here it returns true or false. Anyway, we are getting off track. Either turn on output formatting before $event->message, or simply add first() before url and you should be fine. Does that work or not?

Yes, why? I didn't read the readme (this time). I didn't look closely enough at the requirements written on the profile homepage (demo or localhost). And/or I didn't want to install the DEV version (I've never done it). I hope I can come back to the MASTER version with the upgrades module once the new master is out. Perhaps my mind filtered the information.

This is the usual array of images problem - either add first()->url, or set the image field to only accept one image.

@bmacnaughton. That's not what I meant. What I meant is that ProcessWire offers you a number of tools to sanitise values. Depending on whether you are a frontend developer vs, say, a module developer, you will probably be using a subset of tools more than another subset. In other words, at the end of the day all input should be sanitised; the tools you use will vary depending on the job at hand.

Hi, I am not familiar with the specific settings and configurations for the CKEditor, but I've found something: Have you applied this to your field using the CKEditor? Maybe <br /> works? ~Harmen

Sure, that will come handy, thanks!

Tom, why? Is there no room for 3rd-party Admin Themes in the future available via the modules' directory? You know how it is with subjective preferences; some people will prefer Reno others will prefer the new default theme (when it comes out) . Just wondering....

For reference, here is the bug report https://github.com/processwire/processwire-issues/issues/187

Perhaps I should add another variable ($ppid - protected page id) to the array that is passed to wireRenderFile. This would be the id of the page that is protected, whether that is the current page, or the parent which is protecting it. That way you could do a $pages->get($ppid)->body to get the appropriate text. Would that be useful? Attached version has this if you want to try it out. Does that idea also help with your multi-language content question? I don't think I am totally following what you need there. PageProtector.zip

How are you all envisioning the pagetree working in the sidebar for large sites? Or do you just mean having it configurable to use if it works? I have sites where the nesting is far too deep to make the sidebar pagetree useful.

+1! If would be awesome if the page tree could be visible in the sidebar. The Page Tree and ProcessPageEdit seperately are to most clients instantly clear, but combining those two would fill in a gap.

It would be helpfull if we could see your template files and includes (like footer.inc), I suspect there's still some mistake there - Oculi plus vident quam oculus

It works with that directive added. Thanks flydev! So the formula to install Processwire on Ubuntu on Amazon EC2: sudo apt-get update && sudo apt-get upgrade -y sudo apt-get install apache2 sudo apt-get install lamp-server^ sudo apt-get install php7.0-zip sudo a2enmod rewrite sudo apt-get install phpmyadmin sudo ln -s /usr/share/phpmyadmin /var/www/html/ sudo adduser ubuntu www-data sudo chown ubuntu:www-data -R /var/www sudo chmod 2775 -R /var/www sudo find /var/www -type d -exec chmod 2775 {} + sudo find /var/www -type f -exec chmod 0664 {} + sudo service apache2 restart Then add this directive to your VirtualHost in /etc/apache2/sites-available/000-default.conf : <Directory /var/www/> Options Indexes FollowSymLinks AllowOverride All Require all granted </Directory> And then it should all work. ...still have to see it working with my custom exported profile, but that is my problem. (Edit: that was caused by syntax errors in my custom templates, unsupported use of short_tags.)

In case you would like to try another module:

Hey @bcartier and everyone who is following. I implemented a basic language support. Nothing really changed, except now with LanguageSupport enabled in your ProcessWire app, the GraphQL api will return the content in whatever language the user is assigned. In addition, when Language Support module is activated, there is a language field in your GraphQL api. So you can request the exact language you want. It looks like this. { language(name: "de") basic_page{ list{ title summary } } } You need to put the language field on the top. Well, not exactly on top but just before fields that return translatable content, like title, headline, body etc. It's because GraphQL processes requested fields from top to bottom and it will not know what language you want till it gets to language field. Did you also know that in GraphQL you can query same field multiple times with aliases? Here, take a look at this { basic_page_default: basic_page{ list{ title summary } } language(name: "de") basic_page_de: basic_page{ list{ title summary } } } Curious what will be the response? Try this with site-languages profile and find out.

Ryan says in his new blog post: "For instance, if you like a 2-column layout (like Reno) rather than 1-column layout (like Default) then that's a simple matter with the built in grid system. Nothing is set in stone, and our focus is on establishing the system to provide the path and flexibility for it all." also: "So what I've been doing here is coming up with a basic admin theme profile that the skilled designers in our community can then run with. My hope is this will be a collaboration where we'll come up with the best admin themes anyone has ever seen for any CMS. As a community, we'll want to select one or two that we can also bundle with the core in ProcessWire 3.1 as well." Well, +1 for a sidebar, but even better to have a setting that moves the menu from the top navbar to the sidebar and vice versa

It might be obvious but I would like to point out that this would be the right time to implement most (if not all ) of the features of AdminOnSteroids which means at least a built in admin theme settings page to customize things to our liking, similar to AOS. However, there are features in AOS which can even be made better when implemented as integrated parts of the admin theme, such as "hiding"/revealing the Descriptions and Notes of fields. Having Descriptions and Notes around is extremely useful, but only in "development mode". When things are set up, they just take up space, distracting navigation and focusing, so I generally "hide" them by AOS (turning them into tooltips), but oftentimes I disable AOS, just to be able to skim through them quickly. Enabling/disabling AOS is not the best solution, because I loose all other functionalities of the module, but a native admin theme feature like this would only switch the relevant option of the admin, not all the others all at once. This can even be taken to the next level by being able to specify it on a field-by-field basis. The above mentioned example is just one, AdminOnSteroids is full of handy-dandy goodies that could boost the new admin theme a lot if implemented in an integrated manner.

@Nurguly Ashyrov I really like what you do here! So much fun to see this. Unfortunately I have no time ATM to start playing / using it. (buhuhh, - schnüff)

@Oliver, @bcartier Thanks guys. Glad you like it. No, Language fields are not supported yet. There will be support for them too. Maybe I will implement them this weekend. In any case I will let you know when they are available. For those who are following this module, I make releases almost everyday. Sometimes I introduce new bugs but patch them as soon as I find them. There are bunch of features added since the first introduction. You can follow up the changes/additions in the changelog. Lots of parts are not documented yet but I will provide full documentation and possibly introduction video targeted to ProcessWire users, on what the module is about, how you can use it, along with some todo app tutorial. But for now, feel free to play with it and provide some feedback either here or in issue tracker. It is always easier to make changes in the beginning.

You can certainly do it using page tables or the profield matrix, but often people don't like the UX of those fields to much for this use case. But it's the best we've got for that kind of content – and seeing that silverstripe UI I think it's not so much a problem for you.

I have already started to build upon the new site profile: http://szabesz.hu/ I replaced uikit.min.css and uikit.min.js with their currently up-to-date counterparts (3.0.0 beta 9, February 3, 2017) so it looks OK in IE and Edge too.

$this->modules->get('JqueryUI')->use('modal'); After that you should be able to see the modal if your link has the "pw-modal" class. If you need to add buttons to the modal, follow the instructions in "\wire\modules\Jquery\JqueryUI\modal.js"

Hi tpr I've just passed through the same problem. The solution is to give the location/name of your twig file as the second parameter. Ex: {{ __('my_string', 'home') }} for templates/home.twig or {{ __('my_string', 'includes/header') }} for templates/includes/header.twig

If you want to use the values sent as.. email value use $sanitizer->email name for a ProcessWire page that you don't care if it has upper case letters use $sanitizer->name. Name is used to build your url so this will be my-Upper-Case-URL name for ProcessWire page that is more friendly $sanitizer->pageName so url will be my-lower-case-url a valid selector string use $sanitizer->selectorValue a valid string for a ProcesWire page $sanitizer->text etc Unless you are a developer (and even then this is rare) you will not need $sanitizer->fieldName or $sanitizer->selectorField. Note, you are not limited to using the above according to my examples. For your own needs, you may want a string to be cleaned to remove dashes, etc. So, you can use $sanitizer->name in that case... If the above still doesn't make sense...I'll eat my hat

Thanks for this. In the comments of the Calendario article there is this: If we were to use a different field than 'title' for the date so we could have multiple events for the same day, how can we check for the same date and join those event titles/descs? Or would it be wiser to integrate a more complete solution like http://arshaw.com/fullcalendar/ Btw. fullCalendar supports event descriptions as well: http://arshaw.com/fullcalendar/docs/event_rendering/eventRender/