Leaderboard

So after some smalltalk to Luis and some xmas madness...it's all there as kind of little christmas present. A OS siteprofile released under MIT so it should be easy possible to use parts of that profile in own projects and keep credits to the original creator. Github Repo: https://github.com/mr-fan/Officesuite Thanks again to Luis for his permission to release it to the community. Best regards mr-fan

ALIF - Admin Links In Frontend EDIT: latest version update with PHP 8 fixes on 05. Nov 2023 (!) The version now is 1.1.9 (!) This module combines some of the admin links that we want to use on the frontpages sometimes. It is a comfortable and easy way to do so. After you have installed and configured the module, you can inject the links into the frontpage with code like this in a template file: echo $modules->isInstalled('AdminLinksInFrontend') ? $modules->get('AdminLinksInFrontend')->render() : ''; . Credits: The comfortable Javascript Color Picker in the Configpage comes from Jan Odvarko (http://jscolor.com). Many thanks for this! * Toolbar The toolbar can be positioned by css values for top/bottom and left/right. It can expand in vertical or horizontal direction. The buttons are links to the PW admin, for logout, or for editing the page in admin, or informational ones. All settings, including the colors, can be defined in the modules config page. This is available for all PW versions from PW 2.3 up to now. Depending on how you configure this part, it can be used for authors and editors too, maybe. * Import / Export Settings It has the possibility to export and import its settings via two textarea fields. When importing settings, you get a second screen where you can select which settings you want to import. * One-click User Account Switcher For PW versions 2.6.8+, there is one really nice function available, that I use when developing / testing sites with different user / roles. A fast User-Account-Switcher that lets you view the same page from different user accounts with only one click. To enter this mode, you need to login as a superuser one time, and the feature needs to be enabled in the module of course. After that, you can log out, login with different user roles, etc. At least the toolbar buttons for the User-Account-Switcher will stay visible for you. This is session based. There is also an extra button with a trash can and the text "Session", that helps you to leave this mode once you are finished. As you can see in the screenshot, after clicking "guest", I was logged out, but a regular login button, a warning for debug mode and my three defined buttons for user accounts are available. When clicking another user button I login with this account. Very handy. ATTENTION! The use of the One-click User Account Switcher is mainly intended for dev sites, not for public sites! You should be aware that there is a huge security risc when using this feature on public reachable sites! We completly leave ProcessWires comfort zone in regard of security, - and the only thing between your site and potentially hackattacks is this module. (Oh mom, - what have I done?) PW 2.6.8+ has a comfortable function for admin tasks, that let us log into different user accounts via API without using passwords. This module uses this function! All data that is needed during a User Account Switcher session is stored in the session data on the server. So, if someone steel your session cookie, there is potentially risc that he can login as a superuser, depending of the user account buttons you have in your admin links collection! To prevent SessionHijacking, the module can be bound to a single IP address, it uses a fingerprint depending of IP(s) and UserAgent string. And you need to define a max time to live in minutes between 2 and 60, a User Account Switcher session may run. A User Account Switcher session only can be initialized by a Superuser who also explicitly has set a permission called 'alif-user-account-switcher', what is defined by the module, when installing it. So, the prefered way to use this module is, to enable and use the User Account Switcher while the site is unpublic, and before it goes public, remove the permission from the superuser role. This way, you can use its menu function, but not the UAS anymore. On a sidenote, for those rare cases where multiple superusers simultaneous developing on a site and want to use the ALIF, but the UAS should be used only by one, you can leave the 'alif-user-account-switcher' permission removed from the superuser role, but need to assign the role 'alif-superuser' to the single user account. This way, only that single superuser has the permission for UAS, whereas all other superusers doesn't have it. . . * The Configpage * Online demo I have pasted it into this old site and enabled it to be present every time (when the site is in demo mode only!). So, it is an earlier state, but the switcher is functional there: http://pwlaf.biriba.de/dbinfo/ * Download From our modules directory or from github repo

Hi all, With December being a busy month for me, I'm not had time to work on this. I should have more free time during the New Year. I'll hopefully then be able to throw up some code (Github) for others to look at and tear apart etc, and a demo etc. @pwFoo HBB will also be lightweight at the core, with just the needed features for a basic forum. As you say, plugins/modules etc could add other functionality if needed. I won't be adding features like tags, likes, notifications etc into the HBB core as PW can handle all of that in a variety of ways, and people may already have modules installed that could be utilised for that purpose. My plan is to make it all doable for the forum member from the frontend, i.e for them to be able to post and edit their content without ever seeing the admin area. How this is done via the frontend will be up to the developer of the site that HBB is installed on. This will allow people to use whatever frameworks/scripts they want for the frontend and then HBB can simply store the data when requested. Well that's my big plan at least. A simple forum that can be extended in an unlimited amount of ways thanks to the power of PW. I love the fact that I can just add a new field to the user template, i.e for a profile picture and then this can easily be used for HBB if needed. Anyway, I'll throw up some code soon enough, and then everyone can see whether or not I'm on the right track.

I'm using it in a low-traffic site since summer 2015 and no reports of problems so far from users.

Here is a discussion about the problem and link to the commit that fixed it in Oct: https://github.com/ryancramerdesign/ProcessWire/issues/1451

Hi Tom Thanks for the order! I have messed up my email template (you are not first one that missed those). I'll send you download links again when I get to computer. Some of you have thought about customer portal etc. That is definitely possible to do. I have also talked with Ryan about having private forum for Padloper here at the pw-forums. I'll plan to release 1.1 version this month or early January (including one page checkout) and will email all customers then about new release and how to get access to it.

ProcessWire Email Obfuscation (EMO) Download | GitHub Email Obfuscation module for email addresses with 64 base crypting. This module finds all plaintext emails and email links from the document and replaces them with span elements including configurable replace text. All the addresses are encoded to 64 base strings and stored in spans data attributes. Then on client side we decode these strings back to their original state. Install Create new 'EmailObfuscation' folder into /site/modules/ and place the content of this repository into the directory. Login to processwire and go to Modules page and click 'Check for new modules'. Find 'EmailObfuscation' and click install. You can make optional configuration changes in the module admin page. Thanks This is a ProcessWire module fork from MODX Evolution plugin emo E-Mail Obfuscation. http://modx.com/extras/package/emoemailobfuscation EDITED ON: 2013-03-03 - Added description. 2020-04-16 - Fixed GitHub links and updated description. Hello all. Just found PW few days ago and it's already looking awesome! Here comes first contribute and some questions for developing it further. There was one existing email obfuscator on reposity that didn't use any crypting for addresses so I decided to do a little test run and port the one that we currenly use with MODX Evo to ProcessWire module. I'd like to make PageAutocomplete like gonfigure option to admin so that one could select and set templates to exclude module action. It looks like autocomplete is tied to pages and since templates are not set to system as pages this is option is no go, am I right?

OK, thanks! I've just pushed a fix to module repo. Please update and see if it works for you.

Tom, check your PageFrontEdit module settings page to make sure you've got the option enabled to allow editing of pages other than the current. This is a new option added in 3.0.2. previous versions let you edit anything anywhere, whereas this version let's you lock it down a little more, and it comes that way by default. but you can turn it off from the module settings page.

Maybe EsoTalk and particularly its successor Flarum could be inspiration. I started such a basic discuss module (just some code for testing, nothing which could be used yet) but stopped it because of lack of time.

My stopped "discuss" module was as simple as possible. The base module was planned without an admin / moderator panel and it should just take care about add and edit (own) posts and a structured view (EsoTalk / Flarum like discussions, also with user based view permissions for private topics instead of private messages). At the moment I haven't started an Flarum integration (no time and it's beta), but it could be interesting in the future. HermodBB could be interesting, but strategic focus should be the frontend and usability (at the beginning PW backend would be fine to administer / moderate the boards and posts). My key features tag based structure instead of categories / page tree private conversations by tagging topics with allowed users (or groups?) ajax notifications (PW notifications module?) about new replies and changes in the actual view All other stuff ("like" feature, backend, ...) should be added as optional extensions / plugins (PW hooks)

Hi, the module is listed as unstable because I don't use it with a production site at the moment and there isn't that much feedback about production usage yet, but I think some members here are using it. Reported issues should be fixed. The module IS designed as a starting point and easy to extend by writing plugins (based on PW hooks) without hacking the module itself. *UPDATE* You plan to build a PW based forum? https://processwire.com/talk/topic/11201-hermodbb-basic-bbforumcomments-module

Strangely enough, upgrading has fixed the issue.

No funk on your side: getValues() was the method to get the array without the keys.

You can always use the array_values() function to get an indexed array. array_values($page->logos->getArray())

@GuruMeditation, I'd like to help out.

I just added a couple of new options to this module that allow for automatic protection of unpublished and hidden pages and their children. I am finding the unpublished protection very handy as I can set the parent of a branch to unpublished while it is being developed. With this option enabled, I can send the link to this page direct to clients and they will be presented with the custom login form so they login and then immediately view the page - no need to go via the backend admin panel (just like the normal way this module works), and they won't get the 404 page if they attempt to visit when logged out. Because children can also be protected there is no worry about someone guessing the URL to subpages, the entire branch is protected based on the publication status of the parent. Once the branch is ready to be published, simply publish and it will be live and the protection is removed - no need to give clients access to the control of this module on the settings tab and explain how they work. Hope you all find it useful!

It's been more than 9 months since I wrote in this thread about our intranet. Well, things happened that had me away for a good while, and when I got back to it, the wishlist exploded. Finally, though, the migrated intranet is up and running, and based on the feedback I'm getting, I can already call it a success. Here's a short feature list: Running on Windows Server 2012R2 / IIS 8.5 A little over 8000 pages, two languages, 600+ frontend users in 15 countries, 45 editors About 20 templates 15 custom modules Reduced custom CRM module code to less than one-eighth (counted in bytes, not lines) Integrated web server authentication and detailed Group permissions using Apeisa's UserGroups module (big thanks there! Keeping our group-based permissions was one of the main requirements for the new CMS) Live user + groups synchronization from Active Directory Granular search via OpenSearchServer (including permissions handling and indexing linked PageFiles) Tag based in-text translation system through custom Textformatter module linked to our ERP database, with own CKEdtior plugin (think detailed technical data sheets where you don't want to edit every language version separately) About 400 dynamic pages that range from simple database-driven lists to rich single page apps Persistent page links using page IDs that get replaced on save + render Versioning for textareas Custom links in the style of "article:CUSTOM_UNIQUE_FIELD" used to fetch recurring content into pages in our in-house manuals Booking system for our inhouse training center using just pages, standard fields and a bit (well, a good bit) of frontend-editing glue, with graphical interactive calendar Pages can be published per language through a multilanguage checkbox, with corresponding indicator icons and actions in ProcessPageList Notice board system (title, short body, optional attachment, expiry date) for main and department pages, with frontend adding/editing and admin interface Detailed permissions reports in backend and through command line for compliance audits Not yet implemented, but a working prototype is already on the test system: a simple question/linear response forum system with rating, tagging, answer accepting and highlighting options, primarily targeted towards international knowledge exchange Big thanks to Ryan, PW is really an outstanding system in terms of flexibility, scaling and ease of integration, and also to everyone who contributed in any way to PW itself or its huge module repository. As a funny side node, I talked to a colleague from manufacturing when migration was still under way, and he was initially a bit miffed that I'd swap the system he already knows (hey, it's only been 7 1/2 years!) - but only until I told him I'd use PW. At the mention of the word "Process" he immediately determined that his workflow to add content would get a lot smoother, something I could confirm without thinking. (The old system had a separation between categories and articles, so you had to create both in different backend screens to get a navigation entry for a simple page that shows just some text - in PW he only needs to tick the "Show in Navigation" checkbox for his new page.) Shows that the right naming choice already gets you halfway to the goal Now that "The Big Project" is done, I'll only have to weather the usual end-of-year-craziness, then I'll get my custom modules into a shape where I can share them (meaning: polish documentation, add reasonable defaults and switch to module config fields instead of config files).

Loving what is going on here. Excited to soon see the product

I absolutely need a solid front-end user system solution. Of the 20+ PW sites I've built, 2 have required extensive front-end user systems and I've had to kludge together crazy solutions built from bits and pieces of code strewn throughout this forum. It's hack, bad and just waiting to fall apart. PW is such an awesome solid system and it makes me sad that it's so let down by this one critical area. Almost all other major CMS/CMF's ship with some decent front-end user management. I would easily pay $100 for an up-to-date decent system. Or $30 with a yearly subscription like Ryan's other modules. Ryan could probably bang this out in one night (haha ok I'm kidding, but I'm sure he could do it easy enough). Ryan please! There's a desperate need for this. The existing half-implemented modules and bits of code are NOT a solution at all! Please save me from having to use ModX again just because of front-end user management.

Hi, FrontendUser base module is simple and small. It should be extended with sub modules and plugins based on PW hooks. I wrote it because there was no universal and extendable frontend login / register module. PW modules are optimized for backend usage (inputfields, login, ...). Would be great if the PW modules would also work in the frontend, but that isn't targeted / supported.

No offense to the developer of FrontendUser, but I'm cautious about using modules that provide functionality that are core to a project's success. I came from the WordPress world and was burned more than once on plugins that were no longer supported by the developer. I'm at the point where I would rather spend $100 on a module and be confident that it is going to be supported rather than using a free module that may later be abandoned. Yes, basics like registration, login, change password, email address, name, and upload image would need to be supported, allowing users to edit their profile using a custom front end template without having access to PW's back end admin.

http://blog.keithcirkel.co.uk/how-to-use-npm-as-a-build-tool/ Follow-up to this: http://blog.keithcirkel.co.uk/why-we-should-stop-using-grunt/ There are problems on Windows (surprise?). This approach looks appealing to me after just having set up Foundation with the whole Grunt shebang. The idea is that you face the same learning overhead with the configs of a build tool as with the options of a specific command line utility, so why not use the command line utils via npm? Build tools like Grunt or Gulp also bring other types of complexity to your workflow, especially as time goes on and backwards compatibility breaks somewhere in your toolbox.

WireArray types may be associative and are designed to support direct access via indexes. So you could have a collision with a WireArray that has a index of "count" (or one of the other suggested direct access properties). While it's certainly feasible to support that for numerically indexed WireArrays, I'm reluctant to introduce conventions that can't stay consistent across WireArrays.