wbmnfktr

Had to play around with it and it works like a charm. Thank you @Kiwi Chris for sharing this. This will come in handy for smaller sites or prototypes. What I really like is that saving pages from the submitted form doesn't need an extra step as it does in FormBuilder. The created template is already the form and the template for the pages.

I really like the idea and the direction this article takes but there is one thing that ... has some kind of aftertaste. You are writing ProcessWire ist sicher (ProcessWire is safe) and telling people that there are no documented security issues but linking out to a page that tells something different - at first people will only see: Github ... ProcessWire... Issues... Security... security... security... I know about PWs high level of security but even I had to take a much closer look at those issues. Your audience could get this horribly wrong without further explanations as they will not dive deeper into those issues.

These are the Bypass options ProCache provides. Hope this helps in any kind.

Just stumbled across these (marked in the screenshot)... you might want to fix them and the og:image/twitter:image:src paths. But yes... as @DaveP mentioned: super clean code and clean site.

Instead of loaders: skeletons Like Facebook and even this forum does for embedded content like the preview above.

_init,php isn't a regular template file. It's more kind of a universal settings file with variables and presets you might need later on your page(s). So you could add the following line to site/config.php $config->prependTemplateFile = '_init.php'; The _init.php in /site/templates/ will be included every page load and therefore the login check is always in place. Within this file you could and should add psy's / your code <?php $loginPage = $pages->get('template=loginregister'); // in my case yours might be different if(!$user->isLoggedin() && $page->id!=$loginPage->id) { // checks if user is logged in and not on login page $session->set('returnPage', '/path/to/welcome/'); // set your welcome site $session->redirect($loginPage->httpUrl); die; }; This would redirect every user that is not logged in to your login page and sets the returnPage. Be careful with the check conditions. You might want to fine tune this check.

Have a look at this post: @psy's code does almost exactly that what you need/want. At least you get the idea and can adjust it to your needs.

The frontend looks nice and clean but what caught my attention was the backend. We see lots and lots of frontend but this one is a nice look behind the scenes. I love it! Would be interesting to see or know more about this and some other backend solutions.

@AndZyk MapMarker is a nice module and does most of the things most people want. But there is still some overhead if you build and use your own Google Maps with custom scripts and markup. All @suntrop does and probably needs is grabbing lat/long from Google and saving it to text fields. A super lightweight solution btw. I played around with Profields: Textareas and the lat/long script. Still everything is fine. With and without language support and german language pack.

None of my text fields or textarea fields convert 50.43578373748 to 50,43578373748. Can you explain your field setup a bit more detailed as your description sounds kind of weird to me right now.

Try this: $options = $fieldtypes->get('FieldtypeOptions')->getOptions("optionsfield")->get('id=2')->title; Easier to maintain and for further use: $options = $fieldtypes->get('FieldtypeOptions')->getOptions("optionsfield"); $options->get("id=$yourId")->title;

With your code: $options = $fieldtypes->get('FieldtypeOptions')->getOptions("experienced_in")->title; Much shorter and probably much easier in page context: $optionsId = $page->optionsfieldname; // the ID $optionsValue = $page->optionsfieldname->value; // the value $optionsTitle = $page->optionsfieldname->title; // the title

$static_translations['telephone']['default'] = "Τηλ:<br><a href=\"tel:2821011111\">2821011111</a>"; $static_translations['telephone']['english'] = "Phone:<br><a href=\"tel:+302821011111\">00302821011111</a>"; OR $static_translations['telephone']['default'] = "Τηλ:<br><a href='tel:2821011111'>2821011111</a>"; $static_translations['telephone']['english'] = "Phone:<br><a href='tel:+302821011111'>00302821011111</a>";

Another idea... Create a new parent for each kind of event type. Set corresponding template restrictions in the template settings (family tab) and the users were forced to choose what kind of event they want to create.

You're welcome. Could there be any field name conflicts or Hooks that interfere here in any kind?

In order to complete the testing scenario I added a form to my login page now as well - embed method A, B, and C with FormBuilder form above and below login form. Login still works fine without any errors.

Tested your exact same code with ProcessWire 3.0.79 and PHP 5.6.25. It works as expected with all kinds of users. No entries in the logs or errors on the page. Are there any security or session related functions or modules installed?

Have had the same issue a few days back and got it working by adding this in line 1 of my template. <?php namespace ProcessWire; ?> The translatable strings are defined in this way: <?php echo __('Kontakt'); ?>

Try to load all files (images, scripts, etc.) with a full path including even protocol and domain. So instead of using this: /site/assets/files/1114/livery-corporate.png Try this: http://www.justrightmarquees.co.uk/site/assets/files/1114/livery-corporate.png Maybe this gets the job done: <base href="http://www.justrightmarquees.co.uk/" />