Leaderboard

My goodness, that's a long time ago. Key thing for me is @renobird's answer to my original question on showing the user template in the backend. After that, you can add any field at all AFAIK to the user template. 'In PW everything is a page'™ and user pages are no different. Kinda feels dangerous/wrong if you're coming from other systems, but it isn't.

The register page is disabled deliberately. I don't want anyone registering at this time because we were inundated with spam accounts. As for the coverage of PW 3... we do our best to cover what we can but sometimes news articles don't get much traction. I prefer editorial pieces and reviews. Of course, I'm only one man so while I do have an author or two I pay, I can only do so much. I welcome anyone who wants to contribute PW content, however, and will happily link back to your website in return. Just hit me up at mike@cmscritic.com Thanks

Hi @desbest

You probably are using php 5.3 or lower. Change hosts or ask the current one to upgrade.

Hi @Chamche, and welcome to the forum! The permissions look right. I see that you registered your domain a few days ago, so dns has had time to propogate. Are there any error entries in your log files? You can copy a test index.html file to the public_html folder to see if it displays correctly. It only need contain some generic text. If it does not display, then it would indicate an error with the server setup. If it does display correctly, then it would indicate possible corrupted ProcessWire files when you copied them to the server. If so, then you need to delete all of those files (not overwrite them) and re-upload them. Preferably using ftp. Again, welcome to the forum.

Ok, got the class working now: { name: 'Generic List', element: 'ul', attributes: { 'class': 'generic_list'} } So I create a standard list with the bullet list button, select it, then choose my custom style... ...which outputs: Sweet! And then I saved the page, and the class stayed there in the source, no ACF removal. CKEditor always strips stuff like this out when I add via source, but I guess using this custom file is instructing CKEditor to leave it alone.

This is a minimalistic website for the german architecture office Weissenrieder Architekten BDA. The front-end uses UIkit 2 and Isotope for the projects overview. Every project category can be accessed in the overview with an URL segment. ProFields Table was used for the project detail view. www.architekt-weissenrieder.de Modules used: AdminThemeUIkit Table ProCache Markup Sitemap XML Email Obfuscation (EMO) Jumplinks Tracy Debugger Regards, Andreas

Hello @Dee Welcome to ProcessWire! As stated above, it is recommended that you familiarize yourself with the "manual" (more like semi-automated) standard installation process. I wrote a step-by-step guide for cPanel, you might want to check it out: http://szabesz.hu/blog/install-processwire-in-a-subfolder-on-shared-hosting-cpanel_ins-sub/ In my tutorial I explain how to install websites running "side-by-side" from the same cPanel account, you might want to stick to it. When I'm writing about the "Regular Site Profile", just use this one instead: https://github.com/dadish/pw-skyscrapers-profile as currently this is the only easily installable up-to-date version of Skyscrapers Profile. Please read the "Warning!" in its readme to make adjustments as described (FieldtypeMapMarker dependency). The other profile I recommend exploring is the "Regular Site Profile". These two should give you an idea of how things are wired together with ProcessWire. Have fun with ProcessWire and just ask for help should you get stuck.

I would recommend learning how to install it manually. AFAIK profiles are installed when you install the system itself, because a profile is a complete, self-dependent collection of data, templates, modules, functions and a front end that all work together. In terms of the cPanel automated backups, perhaps you can still have automated backups, even if you don't install PW using the cPanel installer. In terms of upgrades, i wouldn't recommend any sort of automated upgrades, because with any upgrade you always risk something not working, so you'll want to use a stable version and then don't upgrade it unless absolutely necessary. ProcessWire is not like other CMS that have constant updates and security fixes. Sites run fine for many years on a stable version, and only need upgrading when you requires some feature of a newer version. In the case of upgrading, the process is such that you can fairly easily roll back any upgrade you make (to modules and core). For example if you upgrade a module using the updates module, then the old one gets renamed with a prefix dot. If something goes wrong with because of that particular module upgrade, then you can switch out the old one, but you need to do it using FTP. In terms of playing with the Skyscrapers Demo, it is certainly worth checking out, both the structure in the admin, but more importantly the template files where all of the PHP code is to make the magic happen.

@OllieMackJames Glad you like it There are way too many schemas for me to include in the basic module. I chose what I thought would be the most useful. However you have a couple of options: 1. Use the custom schema option, eg: $jsonld = $modules->get("MarkupJsonLDSchema"); $options = array(); $options["@type"] = "VideoObject"; $options["custom"] = array ( "actor" => "Barney Rubble", "caption" => "What an actor!", ... ); ?> <script type="application/ld+json"> <?php $jsonld->render('Custom',$options); ?> </script> OR 2. Write your own schema and add it to the site/modules/MarkupJsonLDSchema/schemas/ directory. See the other schemas in there and their naming conventions as examples, and feel free to include your video schema code in this topic to share with others. BTW, the link http://jsonld.com/video/ leads to a 404 Error. A much better resource is http://schema.org/VideoObject. Hope this helps psy

Try this reference... Troubleshooting Guide What is your Apache version?

Could be an ownership problem.

Welcome to the Forums, @Chamche Any error messages to share with us: PHP, apache? Also, what is the output in the browser?

Hi @desbest, There are any number of topics and modules in the forum discussing this, google: site:processwire.com/talk/ "frontend login" for a comprehensive list. If you can explain what it is you want to accomplish with your project, I'm sure many will offer up suggestions about which way is most efficient for your needs. Let us know if you have any questions.

And I've now tested it too, and it works perfectly. Thank you @Robin S

I agree with Macrura. I would also recommend to install processwire locally on your laptop/computer and make your self familiar with processwire.

I like it! I've used Shuffle.js (non-jQuery, non-commercial) recently to replace Isotope and it did the job nicely.

Thank you, adrian this... $user_image->first()->url ..fixed my issue of rendering a user image. As you mentioned, even though field is set to 1, I needed to add "first()" I just started using ProcessWire today and I have to say this is the most fun I've had coding a CMS. It's the CMS I'd have written if life didn't keep getting in the way and eat up so much of my time....haha Outstanding job, Ryan!

To my way of thinking, numeric IDs are the worst case in terms of being editor friendly. I see HannaCodeDialog as being a kind of progressive enhancement of Hanna Code, such that in the future you could uninstall HannaCodeDialog and still have tags that an editor can understand and use. But with numeric IDs you'll have tags along the lines of... [[my_tag file="34784" options="4745|9748|8985"]] And that seems contrary to the whole idea of Hanna Code, which is about giving editors easy to understand options while you the developer do the heavy lifting (be it matching editor-friendly names to IDs or whatever) behind the scenes in the tag code. Having said that, I'd like the module to be flexible and let devs decide for themselves how they want to use it. So happy to announce... HannaCodeDialog v0.1.2 Inserting a tag from the dropdown no longer opens the dialog if the tag has no editable options. A new method prepareOptions() can be hooked in order to define or manipulate the options that can be selected for a tag attribute. See the module readme for more. @LMD, you can hook this new method to set separate value and label as per your proposal: $wire->addHookAfter('HannaCodeDialog::prepareOptions', function($event) { $options = $event->return; $new_options = array(); foreach($options as $option) { if(strpos($option, '@@') !== false) { list($value, $label) = explode('@@', $option); $new_options[$value] = $label; } else { $new_options[$option] = $option; } } $event->return = $new_options; });

if ($page->directors && $page->directors->count())

$fieldgroup = $template->fieldgroup; $f = $fieldgroup->getField($fieldName, true); // Do stuff $fields->saveFieldgroupContext($f, $fieldgroup);

Christ, I've just done some serious needle in a haystack work. I found the function that fires in teh frontend in JS: if($img.attr('data-fit')) { fitImageToWindow(); } else { $container.width($img.width()).height($img.height()); } commenting out fitImageToWindow(); works but as the file is minified already I also commented out r() on col 1:8630 of the minifed file to get results straight away: so now the image simply doesnt resize to the size of th window (which personally I feel was an odd choice)

This is so common - I do things like this all the time, not just for menus. Does anyone else think this should be part of the core? For now, I wrote a simple flat function: /** * Recursive traverse and visit every child in a sub-tree of Pages. * * @param Page $parent root Page from which to traverse * @param callable $enter function to call upon visiting a child Page * @param callable|null $exit function to call after visiting a child Page (and all of it's children) */ function visit(Page $parent, $enter, $exit=null) { foreach ($parent->children() as $child) { call_user_func($enter, $child); if ($child->numChildren > 0) { visit($child, $enter, $exit); } if ($exit) { call_user_func($exit, $child); } } } With PHP 5.3 you can generate a menu (or whatever else) recursively as simple as this: visit( $pages->get('/menus/main') , function(Page $page) { echo '<li><a href="' . $page->url . '">' . $page->title . '</a>'; if ($page->numChildren > 0) { echo '<ul>'; } } , function(Page $page) { echo '</li>'; if ($page->numChildren > 0) { echo '</ul>'; } } ); Dead simple. I've seen the options for modules etc. that generate menus - they seem to grow out of control with a million options, and my own helpers seem to evolve the same way, and it doesn't jive with the beautiful, self-contained, simple templates you normally get away with in PW. Would it make sense to have a standard visit() method in Page in the core?