Leaderboard

Somewhere between 60-80 hours, which includes the general consulting, coding, communication and other issues that came up. I didn't track time like I normally do so this is an estimate. Superusers have full access as usual. General users, authors and vendors have access to the pages they are creators of (posts, products). In Ryan's case study from a few years ago, he implemented a hook that prevents users from accessing other user's data in the admin. That part is key. Some CSS is also being used to hide what's not necessary for non superusers to see (along with permissions enforcement). It's easy to load a custom CSS file in the admin based on whatever condition you want it to meet. For example, the following in /site/templates/admin.php if($user->hasRole("author")) { $config->styles->append($config->urls->templates."author.css"); } Thanks for catching that typo. I also updated the chart to link to the various PW modules.

I think it depends on your content approach. For instance, if the client has a complete operation in Brazil, it will be great to both users and SEO to have the URLs also translated like so: example.com/about-our-products example.com.br/sobre-nossos-produtos (.br is optional). example.com/pt/sobre-nossos-produtos (.pt can also be "pt-br" or "br" if you are targeting specifically Brazilian Portuguese speakers) But in the case of just translating the content (not fully localizing it to the market) and/or you already have a bilingual site with the same English URLs, keep them in English only. And on the topic, avoid at all costs using country flags on the front-end. Unless you're targeting specifically like I said.

One of PW 3.010's major novelty was the introduction of Horst's new image resizing engine that uses ImageMagick. Now I understand that ImageMagick can convert images to Webp, the image format that Google says can reduce image size up to 34% compared to JPEG. Mozilla is apparently adding support to Firefox, and even the Safari team is playing with it, so it looks like Webp is soon going to be available in most major browsers. If Horst's module can be extended to add Webp conversion, that would be a great addition to PW's already very powerful image manipulation arsenal. I'm currently using the free ImageEngine Lite to serve Webp images to supporting browsers, and the results are impressive. I routinely get images that are between 25 and 60% smaller compared to JPEG, with the same visual quality. I would love to eliminate the need to rely on a third-party service though.

Updated the module to version 0.8.3 for working with PW 3.x (use version 0.8.2 for PW 2.x).

Do you know if there is a high setting allowed for timeout on this host? If so, you may try to temporarily add a line into your site/templates/admin.php (before the controller.php) $timeLimit = 60 * 15; // sec * min <= adjust to your needs set_time_limit($timeLimit); ------- In general, you also simply can copy all files to a new location. You then will need a mysql dump too. If you have no other tool at hand, you simply can install the PW module ProcessDatabaseBackups, before you do the copy. Create a full backup from within the PW admin, before you copy the files. The backup can be found under site/assets/backups/ database/...

I agree. No need at all for utf8 on urls. PS: good advice with the flags. I hate to see the brazillian flag representing the Portuguese language in international sites, and I'm sure Brazilians feel the same when it's the other way around. A flag represents a country, not a language.

Good tip! I haven't think about that it could be an issue although the sites I made/designed so far are OK with flags. Seems that I can throw away my fine-tuned/optimized svg flags

No, I actually side with @cstevensjr in not wanting to remove the added security. I do have some additional fixes that have nothing to do with the security certificate issues though, so at some point I'll probably offer those fixes as a patch to the plugin without introducing the reduced security. They primarily have to deal with fixing the way various mail clients and how they handle (or don't correctly handle) attachments and/or inline images.

I'd strongly suggest you to take a look vue.js instead of react. It's considerably more friendly to beginners, but does still have all the powers react does have (not judging advanced stuff like react native). I personally also feel, that react is more targeted to a "all or nothing" usage (at least in terms of tooling), whereas with vue you can start out just by implementing small components in your site, without the need to change everything from the get-go.

Thanks for the update Ferdi! Any chance you could include the PW modules repository link (http://modules.processwire.com/modules/publish-to-twitter/) in your opening post?

Here you go: As you can see it offers a lot better screen utilization, especially on wider screens. It can be similar to WordPress admin if you place an image field to the top of right column (called "featured image" in WP).

v064 is just uploaded: possibility to set admin columns inside tabs using FieldsetTabOpen's Note field AdminColumns: skip column generation if aos_column_break is put inside a tab do not add module JS and JS config to login page

I name them at their original language but usually they are readable (latin). When it comes to cyrillic or chinese characters I would probably use English. But it depends on who will use the admin, and whether to use these names (titles/labels) on the frontend, eg. in language switcher. I would avoid UTF8 page names and urls if there's no specific need.

You should open a work (trouble) ticket with your hosting provider/domain registrar. Sending an email to the abuse address is most likely not manned or properly monitored. There are explicit established rules for hosting providers/domain registrars to handle this type of situation. It may take some time to get this resolved, however the sooner you make them officially aware the better for you. They can also provide guidance on how you, as their subscriber, can alleviate this problem in the future. Additionally, you will then have an official record that there was a problem. You can refuse to close the ticket until the hosting provider/domain register has satisfied your request. Worst case scenario, here is a link to use if all your other problem resolution strategies don't work: http://www.iana.org/help/abuse-answers Furthermore, If you aren't getting any resolution of this issue, I would recommend that you additionally look for a better hosting/domain registration provider. Good luck with this because this is one of those irritating problems that occurs sometimes.

that is really cool - hopefully others find it useful also; i was able to create a 'restricted' role with that permission, and add it to selected superadmins on the project, and now they have a much smaller, restricted set of tracy items – working great! thanks as always!

Ok, check out the latest version. Any panels that are checked here won't be available to superusers (and other users with tracy permission) if they have the "tracy-restricted-panels" permission. Let me know if that works for your needs.

Don't forget about $this->halt() rather than using exit/die https://processwire.com/blog/posts/processwire-2.6.8-brings-new-version-of-reno-admin-theme-and-more/#new-this-gt-halt-method-for-use-in-template-files

This module is improved and extended successor to Version Control For Text Fields. It handles everything it's predecessor did -- providing basic version control features for page content -- and quite a bit more. Download or clone from GitHub: https://github.com/teppokoivula/VersionControl. This module requires ProcessWire 2.4.1 or later, mostly because of the file features, which require certain Pagefile and Pageimage methods to be hookable. There's no sensible way around this limitation; for those stuck with < 2.4.1, Version Control For Text Fields will remain a viable option. What does it do? While editing pages, fields with old revisions available show up with a new icon in their header bars. By hovering that icon you get a list of available revisions and by clicking any one of those the value of that particular field is reverted to that revision. No changes are made to page until you choose a revision and save the page, which means that you can keep switching between revisions to get an idea what's really changed without inadvertently causing any content to change. The module also adds a History tab to page edit. This tab opens a view to the history of current page in the form of "revisions" -- each of which is a group of changes to page fields processed during one page save (similar to revisions in various source control applications). There are three actions you can perform on these revisions: adding comments, live previewing what the page might've looked in that revision and restoring the page to specific revision. One specific feature that has been a big thing for me personally is support for file (and image) fields, as the original version control module felt rather incomplete without it. I'm hoping to take this a lot further performance, stability and feature wise, but as it stands right now, it's already included here and should be fully functional. Watch the video preview here I prepared a little screencast outlining most of this: http://youtu.be/AkEt3W7meic. Considering that it was my first screencast ever, I'd like to think that it wasn't that bad.. but I might give it another shot at some point, this time planning a bit before hitting "record" Upgrading from Version Control For Text Fields For those already using Version Control For Text Fields, I've added something extra. If you upgrade that module to it's latest version, you should see a new checkbox in it's settings screen saying "Don't drop tables during uninstall". If you check this, uninstall the module and then remove it's files (this is required in order to install Version Control), your old data should be automagically imported to Version Control. Import has only been tested with limited amounts of demo data. Proper tests are yet to come, so please be careful with this feature! Update, 21.6.2015: as of today, this module is no longer in beta. While all the regular warnings still apply (making changes, including installing any new modules, on a production site should always be considered risky) Version Control has gone through pretty extensive testing, and should be as stable as any other module out there.

@Sérgio - that's a great case to make your point - I really appreciate your (and everyone's else) feedback on this - it's been very helpful. I'll be diving into the frontend side of things tomorrow so I am sure I'll have some more questions. Obrigado a todos

Imagine this case: - The site has English as default language and Portuguese (pt-PT) as an alternative and you decided to suppress the language code on the URL, like in your example above. Everything looks fine but a new page is added with a name that is ambiguous, like '/actual'* (which is a false cognate, as it means 'current' in Portuguese). Event if PW's handle the routing fine, what about the users? What language is the page in if they only see the URL? So, a pt/actual/ will be better. * 'Actual' is used just as an example, as it's now spelled 'atual', after Portugal, Brazil, and other Portuguese-speaking countries agreement on vocabulary issues back in 2008 I think.

I agree with @tpr on avoiding utf-8 URLs, like, "/pt/apresentação/" for (/presentation) as there's no real need of it for Portuguese. Avoid flags to represent languages unless you're targeting a specific country > language. Eg. Brazil's flag for text is in Brazilian Portuguese, not Portugal's flag and vice-versa. This is only a UX good practice, though. Language switcher is fine. PW's language profile is a good example, although you can only show the language's abbreviation instead of its full name, so EN and PT are fine. I still prefer PT instead of BR unless you will have both Portuguese versions of the site, in this case, use BR ou pt-BR / pt-PT. Regarding the domain, Google has a good documentation about it: https://support.google.com/webmasters/answer/182192?hl=en

yes i would do piwik in a subdomain

I think it should be "Português" because it's directed at people that want the content in Portuguese. Usually that doesn't make much difference, but think of the extreme case of a website in Chinese (again Chinese, but for the other question) — if you have the language links in chinese, the people to whom they concern won't understand them.

done that

And of course update the module compatibility to include 3.x

I see, I though that's some kind of error coming from AOS Tooltips. I would perhaps try using CSS outline, eg. li.InputfieldStateRequired { outline: 2px solid #efcb1d; outline-offset: -2px; z-index: 1; }

@Jonathan Lahijani Thaks for the intel Jonathan! OT here, but any chance of releasing you video tutorials soon?

These are all required fields. I know that yellow is not the best color. I have only tested it to make required fields more visible for the author. Non required fields are with no colored background.

Another usage example: I use it for an event calendar. On the left side is all information about the event as text. In the right column are all settings for the event (single or recurring event, start, end, price,...)

Or use the User Switcher in Tracy so you can test easily https://processwire.com/blog/posts/introducing-tracy-debugger/#user-switcher

In case any new users end up here, just make sure you've logged out all users of the admin area before you're convinced the module doesn't work. Had my 15 minutes of *FacePalm* today.

Whenever I commit a new version to Github I always update the PW modules directory, so you should always be able to get the latest version (which is 1.3.6) that way.

Thanks - I understand that when using "language alternate fields" it automatically used the field based on the language name in the "_suffix" but are you saying it also works if I had two pdfs in the one files field named: "mypdfname.pdf and "mypdfname_portugues.pdf" - so if the user has selected the default English they will get the first one and if they select the dutch language the second one will be automatically linked to instead? I just did some basic testing and I don't see it functioning that way. What does work (and what I assumed I would have to do if I upload all language versions to the one files field), is this: $page->document_pdf->get("name*=portugues")->url obviously replacing "portugues" with the current language. Am I missing some other way to do this? I am actually thinking that separate language alternate fields will probably be easier for the site editors, but I am still curious to know if there is a different approach I am missing.

I got this thing to work though I may change the syntax here and there. Currently it uses FieldsetTabOpen fields' notes where you can enter this syntax: colbreak_seo_keywords:50 Here "seo_keywords" is the field name after which you would like to put the break, and 50 is the percentage. It's all JS but it's not visible at all. I've probably found a PW inconsistency: emptying a field override (Notes) I would expect that the original value is used, but not, it's overrided with an empty string. The same thing is OK for example overriding the field Width (Input tab).

They finally released 1.0: https://quilljs.com/blog/announcing-quill-1-0/

Perhaps they have set up their mail in the similar manner as their domains?

Thank @cstevensjr for the recommendations, I actually submitted a ticket not just an email! Neither NameCheap nor Enom have answered up to now, meanwhile, the .htaccess that Ryan posted did the trick.

I wouldn't like to add 2 or more field to support multiple column breaks. I have an idea to enter field names to the existing field's label (title), and add breaks based on that. But I'm open to other ideas too.

Sweet - glad you are finding it useful. I am kinda keen on knowing what panels you use and what panels you restricted them to. I have actually been thinking about setting up a poll so I can find out what panels you guys are all using - would be helpful so I know which ones to focus on improving. I don't think this new version of the forums has the poll option though.

depends..you could use one PW with multiple page trees and you could limit templates based on those page trees (parents) another possibility would be to use multi-site setup and try the new multi-instance support..this way you can have more cleaner installations as every page uses it's own installation just sharing the same wire folder, but with the advantage of easily sharing data by bootstrapping one page (or more) from another More about multi-instance www.processwire.com/blog/posts/multi-instance-pw3/ for this you should use newest PW 3 (or at least 3.0.30) Note that when using multi-site you always update the core of all sites at once.. If modules will be same and you can update modules for all sites at once you could even symlink modules folder.. If that's a problem you could make independent pw installations and still use multi-instance to share data..

If you want to be picky about it

You can also put it at the very top of the same template file, as long as you do something like this: if($config->ajax) { // Output your json exit; }

New User Bar config settings for changing the position of the bar, as well as an option to also display it for users who also have Tracy Debug Bar permission - gives quicker access to the admin and edit links, as well as any custom links you set up. Also fixed a bug where the User Bar wasn't showing in Production mode.

Okay, that makes perfect sense, and gives me something to go on. I can't think of anything off the top of my head that would be interfering, but I'll have a fresh look. Thanks!

Repeaters have had a major overhaul since that comment by @tpr https://processwire.com/blog/posts/processwire-3.0.4-repeaters-revisited-preview-of-profields-matrix/#major-upgrades-to-repeater-fields https://processwire.com/blog/posts/more-repeaters-repeater-matrix-and-new-field-rendering/#repeater-upgrades-continued-in-pw-3.0.5 and there is also the new Repeater Matrix fieldtype: https://processwire.com/blog/posts/processwire-3.0.4-repeaters-revisited-preview-of-profields-matrix/#new-profields-repeater-matrix-field

Hi guys! I'm really happy to finally showcase this website in the forum. It's the website of a Porto based Digital Animation Studio. A bunch of talented folks, really. This is a heavily animated/scripted/ajaxed website, that makes use of CSS animations, transitions, transforms, HTML5 audio API, and so on and so on. I spent actually more time debugging than constructing it. Unfortunately, we didn't manage to kill all the bugs before the launching, so you might experience some along the way. We even had to give up on Safari (Damn buggy piece of software !!), and advice the user to use another modern browser. But we think it's still well worth it This is also the first website we developed but didn't design. The design is from the excellent The Royal Studio, from Porto. You might know some of their illustration work for the Adobe online tutorials. --- Enough talk, here is the link http://www.aimcreativestudios.com/ (No safari, please, you'll regret it) Hope you guys like it!

@benbyf I forked the module and added the functionality, you can find the module at github: https://github.com/flydev-fr/MarkupTwitterFeed To search hashtag use it as the following : $options = array( 'searchQuery' => 'ProcessWire', 'limit' => 3 ); $t = $modules->get('MarkupTwitterFeed'); $out = $t->search($options); echo $out; The function search() act like render(). Thanks again for the suggestion (searching for hashtag). I think we can improve it a bit, let me know for any needs.

The CSV format is so simple you can easily create a template to generate the right output. As an example: <?php header('Content-Type: text/csv'); header('Content-Disposition: attachment; filename="export.csv"'); $items = $pages->find("template=basic_page"); echo "title,url" . PHP_EOL; foreach($items as $item) { echo "\"$item->title\",\"$item->url\"" . PHP_EOL; }

I just saw this: http://lifehacker.com/5896830/use-google-docs-to-monitor-your-websites-uptime Use Google Docs to Monitor Your Website's Uptime Have a website and want to know the minute your site is down? This simple Google Docs spreadsheet from Digital Inspiration can email you and monitor your website for free.

Great module. Feature suggestion: Would be great if the option to load the dialog could be done via a button on the CKEditor toolbar rather than having to right click to present the context menu. I feel it's too hidden that way.