Leaderboard

I recently started to build Vue SPAs with ProcessWire as the backend, connected with a REST API. Thanks to code and the help of @LostKobrakai (How to use FastRoute with ProcessWire) and @clsource (REST-Helper) I got it up and running pretty quickly and now have put all of it in a site profile for others to use. It includes the REST API with routing for different endpoints, JWT Auth and a simple Vue SPA which shows the process of logging in a user (nevertheless, you don't have to use the Vue part, the API will work on it's own). Check it out here: https://github.com/thomasaull/RestApiProfile I'm pretty sure, it's not the perfect or most sophisticsted solution, but it gets the job done for me… Feedback or Improvements are very welcome Update: This site profile is a module now: https://github.com/thomasaull/RestApi

Same here, padding looks good to me rather than everything all squished up. 27" monitor at 2560x1440 with chrome at 110% zoom. Also use a 13" retina macbook (for sitting in bed lazy coding - my fave) and looks fine on that too So that is why we need that setting Seriously, using the UIkit admin smaller part of the GUI can be seen and used on the very same screen (compared to the classic Default and Reno themes). Some of us do not like loosing functionality (me included) even if it looks better that way.

Thanks for testing it @adrian! and I get what you mean. Yes, LazyCron generally will slowdown, we can even say it will break completely the navigation on the website! and should be used with caution. Duplicator support LazyCron as "last" cron solution. About PwCron, I don't see objection for removing it from Duplicator or maybe it could stay as is for people who want to use it. I added support for running cron jobs without external modules. Its already on Github (I will update the README). You have to call it this way (/site/modules/Duplicator/cron.php) : 0 0 * * * php /www/mysite/wwwroot/site/modules/Duplicator/cron.php >/dev/null 2>&1

here is the blogpost just for reference https://processwire.com/blog/posts/building-custom-admin-pages-with-process-modules/

Hey @flydev - I am finally getting around to trying this - everything works great, but I am wondering about triggering via a manual system cronjob. I expect Lazcron will result in quite a slowdown for whichever user is unlucky enough to trigger it. As for the PWCron module - I don't really like it at first glance because it looks like it is no longer being maintained.

I have heard alot about Django from a mentor, from what I hear it's actually quite a robust solution, so to be honest am a fan of use what's right , I don't subscribe to using Processwire for every type of application most times, I might find myself using Symfony for certain projects because of the flexibility and proper architecture that requires me to handle things and remove certain bundles , but I mostly use Processwire to build sites I want clients to manage, the moment an application has so many custom and specific needs, I would use an application framework, now if I were in Python world, because I don't really like Python i'd use Django for Site management but would prefer to use something light and flexible. Also I think you should state views without insulting, calling people "Fanboy" is not the right approach all the best

this is really a bad idea! with this, you wibes out all other properties of the imgaeSizerOptions: before your correction, the imageSizerOptions array contain items for sharpening, quality gamma etc. After your correction, the defaultGamma is the only one item. All others are wiped out! PLEASE, repeat all other items with there respective values, or use array_merge() !! $config->imageSizerOptions = array_merge( $config->imageSizerOptions, // all items from wire/config array( // overwrite specific items 'defaultGamma' => -1, 'sharpening' => 'medium' ) ); -------- But in @dreerr s case, I can't think of that this is the issue / solution. Disabling "defaultGamma" is usefull if you gets clippings in dark to black regions. According to what @dreerr describes, my first question is: "How does the original image looks like?" If this already has arctefacts, you ever will get artefacts also in quality 100. Where does the source- or master image comes from? What processes gets it passed through before the upload to PW? Any restrictions on upload? (max size?) Maybe you can provide a link to that image online, or via PM to me?

I would like to see a field that acts just like Page Table field but with Repeater UI. Right now the downside of using repeater is that they are not normal pages. There are limitations when referencing them. Their page name is not editable too. Also, They are off from the URL structure. I start to avoid using repeater if possible after I face these downside in my last project. However, the Page Table field UI is not quite user friendly.

Thanks @flydev - it's awesome to have that option - not sure about using a "every 1 minute (*/1)" call as the example though

Seems great. Awesome Job!. Thanks for sharing. I think the JWT Auth may become a module on it´s own. For folks who don´t know about JWT. It´s a standard for Authentication Using Json. https://jwt.io/

@dreerr I had a similar problem in the past and I fixed it by disabling the gamma correction. On your site/config.php add this: $config->imageSizerOptions = array( 'defaultGamma' => -1, // defaultGamma: 0.5 to 4.0 or -1 to disable gamma correction (default=2.0) );

hey, I wanted to show you my latest redesign that i did a few months ago for fun, hope you like it.

Tweak the backend with your client's brand colors, their logo and a nice favicon. BOOM... they will feel like home.

Yup, my server noobness is showing. Looking at how I could disable eAccelerator, I saw that this particular account had PHP 5.4 selected. Turning eAccelerator off didn't do the trick but switching to PHP 5.5 did. Thanks for pointing in the right direction guys

Looks like you are running eAccelerator Opcode Cache. That could be causing you some problems. Just an observation.

Can you try disabling eccelerator in you php.ini to see if that helps?

Just tried out the latest dev version and experienced the new admin area. Damn, this is a beautiful CMS. Can't wait to see how my clients react to this.

Unfortunately, one is not public – the other one not finished (not public either, but I might put in in my portfolio with a screencast or anything)

You could stick: // Smaller margins @global-margin: 5px; ...inside your custom less file which is imported into '/custom/pw/_import.less/ (or straight in pw-theme-reno.less) and recompile the less (npm run compile), then you can make global margins any size you like... This affects all margins though. In order to do just the inputfields, it's more tricky as there are multiple padding variables all over the place which are saved to other variables. This is only a small example, been studying this theme for about a fortnight now and still finding it awkward tracing the variables about. Either it's a really super complicated thing to do, or the less is just written in a complicated way, not sure which: I do think though that you will lose the consistency if you override just the collapsed inputfields, the global margin would be the way I'd do it so the entire admin has uniform padding throughout. @szabesz maybe set global from 20px to 15px and you'll be happy

@szabesz, Yes it appears to be the same issue still present in 84. What went wrong for me was that I attempted to install a module that depended upon another module which was not yet installed. I proceeded expecting it to install the dependency. No joy. So I did a fresh install because I don't trust any errors, regardless of how insignificant they may seem.

Sorry that's my bad I didn't specify clearly. The main function I want from the Page Table is the ability of editing/adding children, while it also has the ability to edit/add pages somewhere else just like repeater but more flexible(choose any parent).

i have a similar need, and have a 'roll your own' pagetable setup, using Runtime Markup; i think once i implement the Datatables Editor (if that ends up being possible), it will be really cool, and much less screen-estate than a repeater interface.

Just a suggestion for enhancement: There should be a means to prevent installation of components out of order. Yes, currently an alert is displayed. However, the user should not be able to proceed at this stage. We should have the module installation either install the dependency (as other modules state, "will install xxx") or have those modules not available until dependencies are installed. Just my $.02

I think profields table would be most suitable for your needs. https://processwire.com/api/modules/profields/table/

hi cloud8888, don't know what's wrong but i had a similar problem recently. I did a hacky quickfix and had no time to investigate this in detail. maybe you can have a look if that is somehow related to your problem?

Feature request: the ability to have backups sent via email as well as saved on the server.

For now, a simple else for the !is_string() check in sleepValue() will get rid of it. It will mean, though, zeroes saved to DB for any blank values. if(!is_string($languageValue)) $sleepValue[$dataname] = number_format($languageValue, $precision, '.', ''); else $sleepValue[$dataname] = NULL;// or '' or 0

I think comparing PW to Django is like comparing PW to Laravel. They are different beasts with different use cases. All of them are Awesome (Althought I prefer Flask, Yarrrg for pirates!) Maybe comparing PW to https://wagtail.io/ or https://www.django-cms.org/en/ could be more fair since they are CMS just like PW is. I think the bottom line of chosing a toolbox is down to simple questions: 1- I like using it? 2- What use cases can I fulfill? 3- Makes my team and clients happy to work with? So just use what is best for the requirements, restrictions and overal context of the project at hand. Not all projects can be done with Laravel, Django or PW. Maybe you can mix both and have the best of them :).

i could post an edited version, this one is very marketing oriented and names my company and other clients, and talks about some proprietary modules... Perhaps an idea is to setup a GitBook that could be collaboratively edited, like an open source book about Why Choose ProcessWire; on Gitbook, the books can be read, or downloaded as PDF, ePub etc.. When i use this document at meetings, i usually print/bind it and go through the points with the perspective clients..

@codelearner I'm not sure if PW is superior to Django. But some of the strong point of PW is ... that we have that PW2.1 installation running since 6 years without any updates. We don't have to, since there's no security update needed or anything else. But updating it to PW3.x is a matter of 5 minutes, and it still works without doing anything. Except switching the RTE editor, not because it's an issue but CKeditor is now the default RTE. From the PW side mostly there's like 0h maintenance over the years. Developing and supporting projects with PW can be a fun task. ... there's a hierarchical structure that naturally represents a website structure that can be squeezed and squashed and moved around without much efforts, build self containing structures and wrap it up with some code. ... build modules in no time for whatever task. It's consistent with using the API you already familiar with. PW admin itself is built using its API. It's easy to manipulate and extend. ... occasionally you'll hear a "I just love PW" from yourself or your coworker. Usually when the deadline is tight and you have make last minute changes that would be impossible in other Systems. How do you come to this conclusion? Have you already developed something 3 months in PW and then built it in Django?

Perhaps if you could give us solid reasons why Django is superior we could have a reasoned discussion. We might even be able to learn some valuable things that could be incorporated to improve ProcessWire, but unfortunately you are only providing responses like: "Only 3 lines of code in Django" If you actually want a reasoned discussion, please ask reasonable questions and provide reasonable arguments for your own opinions. Otherwise there is no point continuing this discussion. Thank you.

This week we have a guest post from Bernhard Baumrock that is a nice introduction to creating Process modules in ProcessWire. Bernhard covers a lot of useful material here and we hope you enjoy it. Big thanks to him for his contribution this week. I've been traveling (Ryan) for the last two weeks, but arrived back in town last night, so next week we'll be back to our regular PW core updates and schedule. https://processwire.com/blog/posts/building-custom-admin-pages-with-process-modules/

Generally agree, we just need less padding: https://processwire.com/talk/topic/17786-pw-3084-–-core-updates-installer/?do=findComment&comment=156119 Maybe by being able to set it in the config? That would be great.

Hi @jaro, I've been having a look at the Repeater issue and the BreakRepeaterFields demonstration. Interestingly, the issue is not that fields are copied from one repeater to another. It is that the module interferes with the listing of fields when the repeater field settings are viewed in ProcessField, causing the fields of one repeater to appear in the AsmSelect of another repeater. So if you check the database the fields associated with each repeater is actually correct despite the incorrect listing shown in ProcessField. But if the user then saves the field in ProcessField it is at this point that the associated fields become incorrect. Could you explain why the module needs to hook ProcessPageView::finished? This method fires on every page view, front-end and back-end. But most of these page views will have no connection to field settings or template settings changing. Instead of hooking this method, couldn't you hook only methods that are related to field and template settings? So some method in ProcessField and ProcessTemplate? And also, the module is looping over all fields on every page view. Could you focus in on just the field that is being edited? So when field1 is edited in ProcessField, just export the data for field1 rather than looping over every field. This would avoid the situation where the data for repeater2 becomes involved when editing repeater1. I should say that I've just had a brief look at the issue so far, so there might be good reasons why the module does what it does.

that's not totally true...

There's no limit. You don't even choose languages from a list, so you can add Martian if you want to. You can also translate the CMS itself for that truly immersive Martian experience.

If you and your site editors have fixed IP addresses you could use mod_rewrite to redirect away from the Admin page based on IP address. In .htaccess, after RewriteEngine On # Define allowed IP addresses RewriteCond %{REMOTE_ADDR} !^111\.111\.111\.111 RewriteCond %{REMOTE_ADDR} !^222\.222\.222\.222 # Adjust to suit the name of your Admin page RewriteCond %{REQUEST_URI} ^/processwire/ # Redirect to home page. Use 302 redirect until finished testing. RewriteRule ^ / [L,R=301]

@msavard have you seen this post? https://processwire.com/talk/topic/3706-how-to-blockredirect-one-user-role-away-from-admin-pages/?do=findComment&comment=46421 Also, there are these modules: http://modules.processwire.com/modules/auth2-factor-ppp/ http://modules.processwire.com/modules/session-login-alarm/

in the install screens, you have the choice of changing the default backend URL to something else. If you missed that step, you can always alter it later

I made a quick (shabby non-centred) demo of something I've been working on, worked out OBS studio just enough to record this. There's no sound but you get the idea. There's also no sidebar, I thought I'd get the theming sorted first then work out how to incorporate that, I was actually thinking a sidebar with 'favourite' links would be pretty cool, which I guess could be a (process?) module. I'll add that to the bucket list. There was a lot of tracing variables about but I'm pretty happy with the outcome. The different colours are controlled with a single line in my custom theme less file and you see the mouse professionally disappear of screen whilst I recompile. Give us a shout if you want to try it, learning how to use github properly is also on the bucket list

There is limited (and undocumented) AJAX 'dependent selects' support built into Page Reference fields. You must use the 'Custom find' or 'Selector string' option for defining selectable pages, and reference the source Page Reference field (that exists on the same page) using syntax like this: parent=page.page_reference_field_name Based on testing I have found: It only works for Select, Select Multiple or AsmSelect inputfields It does not work inside a repeater item

I was on the right track when I posted the snippet above. I suspected that $user->admin_theme is not available until there's only the default theme and apparently that was the case. That's another question why my condition was always FALSE above but it's hard to bugtrack blindly Try v057, it should detect the current admin theme correctly. If there isn't any then $config->defaultAdminTheme is used. Btw, it was the first time I used grabpw.php to install PW (by Soma) which made things a lot easier. It downloads the 2.7.2 version so it's recommended to modify the "SOURCE_URL" to the latest PW version (otherwise you can use the module ProcessWireUpgrade to upgrade from the admin). TracyDebugger's Console panel was also of great help identifying the issue. Otoh I'm not very satisfied with the current html classes solution and regexp implementation. I may rewrite this very part in the future using data- attributes.

I was using Soma's lovely example of how to create a page via the API and began AOK then started getting Fatal error: Exception: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'mynewpage_url3-1075' for key 'name_parent_id' (in /wire/core/Pages.php line 2103) #0 /wire/core/Pages.php(2103): PDOStatement->execute() #1 /wire/core/Pages.php(1161): Pages->executeQuery(Object(PDOStatement)) #2 /wire/core/Pages.php(1055): Pages->savePageQuery(Object(Page), Array) #3 [internal function]: Pages->___save(Object(Page), Array) #4 /index.php on line 248 Then I found Wanze's super comment Problem solved! Posted this just in case a Google search for that error helps someone else.

This is certainly a bug in PW 2.5.26 (dev branch only). I reported it here: https://github.com/ryancramerdesign/ProcessWire/issues/1103

You are not using a PW selector. This needs to be in PHP syntax: if($page->template->name == 'home'|| $page->template->name == 'project' || $page->template->name == 'projects' || $page->template->name == 'posts' || $page->template->name == 'partners'){ But maybe instead you could see if the $page->sidebar actually exists. Maybe that won't work in your scenario, but thought I should mention it just in case.