Leaderboard
Popular Content
Showing content with the highest reputation on 09/15/2017 in all areas
-
https://www.baumrock.com/portfolio/individuelles-crm-und-controlling-tool/ I'm happy to share my biggest and most interesting ProcessWire project so far with you It's a 100% custom office-management solution that helps my client to keep track of all their contacts, projects and finance/controlling stuff. Conception was done back in 2016 and the software is productive since begin of this year. My client is very happy with the result and so am I. Some technical insights: Everything is done inside the PW Admin. I'm using the Reno Theme with some custom colors. In the beginning I was not sure if I should stay with the pw admin or build my own admin-framework but now I'm VERY happy that I went with PW Almost all of my custom Process Pages use my RockDatatables module - there are still some limitations but without it, this project would not have been possible For the charts I used Google Charts and chartjs - both play well together with the datatables and make it possible to display filtered data instantly: also my handsontable module was created for this project to have a nice and quick option for matrix data inputs: Lister and ListerPro were no options as i needed much more flexibility regarding data presentation (like colorization, filtering and building sums of selected rows): invoices are highly customisable as well and easy to create. PDFs are created by php and mPDF by the way: all data is dummy data populated via my Module RockDummyData have a nice weekend everybody14 points
-
This week: A hurricane, no electricity, a new version of ProcessWire on the dev branch, and a new version of ProDrafts that adds repeater support and workflow support. https://processwire.com/blog/posts/processwire-3.0.75-and-a-new-version-of-prodrafts/7 points
-
i would be happy to take over some backend part. i did some quick research on what's present at the moment at processwire.com and it looks like the only reasonable project lead could be ryan. we have the site, the modules directory, the forum, the dev-directory, the blog, store, showcase... i don't know how everything works behind the scenes. but as the roadmap also lists "new website" as a point i think it's at least on ryans wishlist. it would be really nice if ryan could manage to involve the community into this process. also i would really love to see more transparency what this "WE" in my quote of the roadmap actually is... as I stated on some other threads one of my main concerns with processwire at the moment is the quite high bus factor (https://en.wikipedia.org/wiki/Bus_factor) same here: available for that not before 2018, but willing to help wherever i can5 points
-
I think a lot of us would like to contribute, some way or another, depending on skils and available time. But at the end it's Ryan who must alocate time and other resources for this project and take a lead.4 points
-
hi rushy and welcome to the forum! that does not sound good in the pw world you should avoid creating your own custom php files in the root of processwire. it's better to stay with the intended way of displaying pages, meaning you have a page in the backend and a related template. in your case you dont even need another template or another page. you can submit the form to the page itself. lets say you have a tempalte "contact" and in that template you display your form like this: <?php // /site/templates/contact.php ... <form ...> ... </form> just change your forms action to itself and add some additional php code to the top of your file: <?php // /site/templates/contact.php if($input->post->yoursubmit) { // do some checks and sanitization, eg spam-check // log this request echo 'Thanks for your message!'; } else { <form action="./"> <input type="submit" name="yoursubmit" ...> </form> } pseudocode4 points
-
The thing that can potentially allow Table to scale up to a very large number of rows is the ability to paginate the rows, both in output and in the admin interface. Pagination is not enabled by default but is an option. You could probably have 150 rows in an AJAX-loading repeater without a technical issue, but for both Table and Repeater you could have a bit of a usability issue with that number of rows. Imagine dragging a row from bottom to top for instance. And I don't know if that's even possible with a paginated Table interface (how do you drag from the last page to the first?). But these problems seem like they just go with the territory of what you are needing to do and the number of items you need to support. If you think you will work on more PW projects I'd say it's definitely worth purchasing ProFields. It's fantastic value for money, just for Table and Repeater Matrix alone.4 points
-
This must be the most impressive thing I've seen in PW. Hope it was expensive too3 points
-
Yes, and personally I'm up to lend a hand. But we need to organise. Maybe by starting a thread dedicated to setting up a team and starting to discuss things.3 points
-
3 points
-
PageListTrash Allows non-superusers to trash pages directly from Page List (if they have page-delete permission for that page). Not much to say really - the module adds a "Trash" option to the extra actions for pages in Page List. It looks and works just like the Trash action available to superusers. https://github.com/Toutouwai/PageListTrash/ Up to you whether you think non-superusers should be trusted with simpler trashing. For most cases I like the default behaviour where editors have to jump through some more hoops - I want them to think carefully about what they are doing. But if an editor needs to trash several pages then this module might reduce frustration. @tpr, by now you can probably predict what I'm going to say... ...something to merge into AdminOnSteroids?3 points
-
Taking the cue that came up in this thread, I'm taking this first step to evaluate if we have something to go on as to create a new site for our beloved PW. First of all, we'll need a blessing from our godfather Ryan. Then we need to establish a proper team with roles. I'm taking the first step but by no means placing myself as leader of the project. So I propose that whoever wants to contribute, step forward and say what role(s) you can contribute to in this adventure. Myself, having a background in creative direction and frontend development, I can contribute in planning, design, copywriting and frontend dev. To lead the project, I'd tip the hat to one of the veterans everyone knows.2 points
-
2 points
-
2 points
-
These are just demos and often running the default skin. I think Ryan has mentioned a few times he's keen to stress that they're not design proposals.2 points
-
Thanks again @Robin S. I think i'll go with the Profield. As i understand, it should also be frontend editable via a modal. This way i have the best editing experience and at the same time i support the Development of Processwire. Thanks @all for your help.2 points
-
The indentation looks like a bug, I'll check. Branding logo is something I plan to add somehow, I'll get back to this sometime.2 points
-
Installed AOS and Reno theme now, totally taken the editing to a new dimension, nice one @tpr unfortunately it does makes the old classic theme (used on my previous sites) look very dated.2 points
-
Update: just added and works fine, thanks. However, at least a JS confirm could be beneficial because non-superusers can't see the Trash to restore, what do you think? I've done an "inline" confirm in case of the "Delete" action (aos feature), I could tweak it to make more generic and apply to this button too.2 points
-
Sure, thanks! Will try it soon and commit2 points
-
I haven't followed this discussion closely so sorry if I'm missing the point here, but I believe you can override the append/prepend files directly when you render a page with $page->render(). echo $p->render( ['prependFile' => null, 'appendFile' => null] );2 points
-
@joshuag, I think I have fixed the uninstallation issue. I found a few other issues in the module code too - I will PM you with the details.2 points
-
Just something I was trying out recently that might be useful to someone... With the following hook added to /site/ready.php you can adjust the CKEditor toolbar that a particular role gets for a particular field. Use the name of your CKEditor field in the hook condition. $this->addHookBefore('Field(name=my_ckeditor_field)::getInputfield', function(HookEvent $event) { $field = $event->object; // Define toolbar for a particular role if($this->user->hasRole('editor')) $field->toolbar = 'Format, Bold, Italic, -, NumberedList, BulletedList, Outdent, Indent'; }); Or what I find useful on some sites is adding extra toolbar buttons for superuser only that you don't trust editors to use. $this->addHookBefore('Field(name=my_ckeditor_field)::getInputfield', function(HookEvent $event) { $field = $event->object; // Add extra buttons for superuser only if($this->user->isSuperuser()) $field->toolbar .= ', Table, TextColor'; }); You could use the same technique to selectively define other CKEditor settings such as 'stylesSet', 'customOptions', 'extraPlugins', etc.1 point
-
DEPRECATED - this module will not see any updates. I'm short before releasing RockGrid as commercial module. If you are interested contact me via PM this is a preview of a module that i'm working on for quite a long time. I needed it for an intranet office management application that i'm still working on. It makes it very easy to create very customized Datatables using the awesome jquery datatables plugin (www.datatables.net) Download - sorry, removed as it changes too frequently; closed alpha - contact me if you think you can contribute Remarks: The module is intended to be used on the backend. Loading styles is at the moment only done via adding files to the $config->styles/scripts arrays. Also the communicaton to javascript is done via the $config->js() method that is built into the admin and would have to be implemented manually on frontend use. But it would not be difficult of course Installation: Nothing special here, just download + install edit: removed some parts, because i made a complete rewrite of the module (and may not have been the last one)! [...] removed Why i created this module: of course i know @Soma s module but i needed a lot more features and the newer datatables version. also i like to define all the columns as objects and have everything on one place. lister & markupadmindatatable: nice for basic tables but lacks of features to modify the appearance of the cell values (like rendering icons, background colors and so on) datatables provides a great frontend API for filtering, showing/hiding columns, getting data, modifying it... it also plays well together with frontend charts like google chart api in this case: todo / roadmap: reload only one row add filters to all columns (in future also dropdowns, smaller than, bigger than, Regex, ...) make it possible to add table on frontend pages make buttons look like pw buttons make it possible to set settings globally and only for one table provide easy way of colorbars (percentage, red/green), maybe at different positions (left, top, right, bottom) provide easy way of adding action items (edit, show, link etc - visible or onhover) make own layout for tables (topleft, topright, bottom etc to make it easy to create extensions and show messages) privide way of simple javascript plugins (like I already have for row sums etc) provide easy way of handling actions for all selected items (delete selected, update selected...) provide easy way of reloading data (--> easy when using ajax source) easy way of showing/hiding columns excel/csv/clipboard export GUI for table setup processmodule to show different tables (lister replacement)1 point
-
I've just upgraded the forums due to an important security patch being released. There was a bit of a dilemma in that the forum upgrade was guaranteed to break the theme that blended the forum software into the rest of the site design as it was a fairly major release that contained the fix. I chose to upgrade the forums anyway as the security issue was big enough to warrant a little discomfort in the short-term. Please bear with me over the next 24 hours as I get things looking back to normal again.1 point
-
hi everybody, since some weeks it seems that my attachment size is shrinking and shrinking. ATM i have only 1,52MB left and that's not enough if i want to share simple licecap screencasts. i sent @Pete a message but he hasn't read it yet. i also tagged him in another post and got no reply. is it only me having this problem? it's quite frustrating to invest time helping others here and not having the proper tools. i had to upload the gifs on my own server and paste them into the post. if anything changes that will lead to 404s - not the best for nobody. thanks.1 point
-
Indeed, amazing work! I just started exploring PW and am impressed with what is build on it.1 point
-
wow congrats on this hell of an achievement, also demonstrating the power of processwire as an app development framework.1 point
-
I knew you were up to something Great work and also thanks for sharing the modules. Keep it up!1 point
-
48.83 MB attachment limit is silly, I agree. I have already been wondering what to do when I run out of it. And I'm not abusing it either and I also always make sure to upload the smallest files reasonably possible. I could not notice any suspicions shrinking as I checked it long time ago but I will keep an eye on it. Please @Pete give as more1 point
-
Hello @bernhard, it seems like there is a global limit for attachments of 50 MB per user. You can see your space under Profile => My Attachments. For example I have currently 40 MB left. Maybe the limit could be set higher by @Pete or maybe it is the default of IP.board. I am not sure. Regards, Andreas1 point
-
Looking forward to a few of the v2 components making it to UIKit 3. I've about 5 live sites running on it and it's very finished but missing a few sliders, dynamic grid etc. Well worth a look. Lovely framework.1 point
-
1 point
-
There is only a small "downside" if the website is already online. All links from the default language (except homepage) will change so the Page Path History module MUST be installed to avoid 404 errors from previously shared pages, google search etc. Make sure to update your README.md with all these important info.1 point
-
Just WOW!!! My jaw is on the floor! Great work indeed!! Congratulations @bernhard ! Stupendous accomplishment!1 point
-
I think it's safe to say I didn't read Ryans' posts properly. I will hang my head in shame for a few mins.1 point
-
@Mike Rockett nice "trick"! I don't remember seeing that option on LanguageSupportPageNames. I will definitely gonna use that. I'm currently using the language_iso_code field not only on my sitemap but also on site's navigation (hreflang) and the flag icons but I will delete it1 point
-
if you want or need another page (for analytics that could be nice to have) you can just create a new template eg, "contact-success", create a page with that template eg /contact-success and set your form action to that page ( action="/contact-success" )1 point
-
I found the problem. On the new server I could install PW 3.x with the option INNODB. Installation also fails with the default option MyISAM. Now what to do? I need to migrate from the old server with PW2.7 and MyISAM to the new server with INNODB. Is it possible to convert MyISAM to INNODB? Is it possible to install PW 2.7 with MySQL and INNODB? I coud not find this option. Best Johannes1 point
-
I agree, the WP interface is very pleasing to the eye compared to my current bright white admin. The colour scheme is similar to the Apple website, and there's a reason for people liking varied greys and softer contrasts. I was slightly concerned when I saw the new PW uikit demo admin. It was just so white, like the inside of a dentists room. This is one area where I would be quite happy for PW to follow WP. I don't think imitation of something so massively popular is a sellout. CraftCMS has a very good looking admin too. Again, with the shades of grey, darker grey to contrast, soft drop shadows, not too much white. https://www.google.co.uk/search?q=craftcms+admin&source=lnms&tbm=isch1 point
-
maybe you have some other vhost rules active in your hosting settings? some hosting providers have settings to choose a www or non-www version of the site so if the vhost and your htaccess redirect to the opposite it would be an infinite loop.1 point
-
1 point
-
Plus it's a pita to support both admin themes, not to mention the latest uikit-based one (which is currently not supported "officially").1 point
-
Probably not. I forgot to point out that – especially when manually copying files/folders – it is possible to run into permission issues, so you might want to double check that too. Also, you can install the very same ProcessWire version with the blank profile, replace /site, adjust config.php, .htaccess, permissions and you also need to reset passwords in this case because the difference in $config->userAuthSalt in config.php will prevent the login in this case. userAuthSalt is generated during ProcessWire's install process and tied to all passwords, the login process depends on it as a security measure.1 point
-
1 point
-
This module family appears to work fine on PW3 (sans Macura's issue above). @netcarver, please could you tag it in the modules directory to show that it does indeed work?1 point
-
Yes, that's what it boils down to basically. There are several reasons for this depending on the fieldtype to be edited, but in the case of a repeater PW has no idea what you are doing in terms of displaying your repeater output on the frontend - it gives you total flexibility there. So PW cannot really provide an inline frontend interface for drag-sorting repeater items for instance, because there is no guarantee you are even presenting all of your repeater subfields contiguously inside a single containing div. So I think you'll need to resign yourself to modal editing unless you are up for some serious custom frontend interface work. I'm curious to see the existing interface your client is using - it sounds quite fancy. Maybe you could post a video? (LICEcap is useful) Repeaters scale to a medium level fine so long as you use the AJAX-loading setting. I haven't tried Table with frontend editing but I think any fieldtype becomes editable via a modal.1 point
-
Definitely looks easier to grasp I will give this one a try when I have the time to. Thanks for sharing!1 point
-
I'm making progress with all the necessary changes. On my dev server (not git-pushed yet), the following is complete: Languages: Multi-language is sorted. It now renders the sitemap according to Google standards, where a page's <url> is generated for each languages with alternate langs, including current. Method is not the same as above example (page-loop), but expands on the root-first-then-children process - this allows easier flexibility in terms of what we can ignore on a page by page basis. ISOs: Haven't created the separate language ISO field yet, as my my main concern is regarding names vs ISOs. If they are normally identical, then we would only need to declare a proper ISO name for the default language only when its URL matches the default root URL (ie: default URL root = site root). In this case, perhaps it would be better to simply have a module config entry for the default language only? The rationale behind this is that the language name (other than default) should be the same as the iso (for better SEO practice, I'd guess). I haven't yet bumped into a ProcessWire site that doesn't use the ISO for each language name accordingly. If I'm wrong, please point it out, and then I'll use the iso field, per the above example. Or perhaps I should simple allow the flexibility and have the ISO name fall back to the language name if not provided via a field (the default would still need one if it is root)? Image-support: Images are now picked up in all languages, given the process-change. If an image field is not specified in another language, it will fall back to the default language. Support for ImageExtra remains. Priority: not done yet. I'll follow a basic principal with this: if the priority is set on a specific page, then it will be added. Otherwise, the tag will be left out. If this is not the correct methodology, please let me know. (cc @psy) Note: I still need to do some testing on this...1 point
-
1 point
-
1 point