felix

Yay: Glad to hear people using this! Sorry for the late reply: Just saw that you've posted - I follow this thread now to get notifications on updates. You're right. Some propertys don't load automatically and you need to "get" them the way you've stated. There currently isn't a "fix" for this as we didn't classified this behaviour as an error.

Pretty simple: you would create an url slug where it isn't needed/wanted (see the linked post). And (as stated above) redirects would add too much complexity. It's just about structuring things for editors.

Here is another discussion on this topic. I think having some sort of "structuring item" for the backend page tree would be great. This could propably be done with an extension. I would write one if i had the time atm... but I don't. But as there (quite often) is a need for this from us I will talk to my boss if we can give this to ryan as a "sponsored" extension.

This is something i'm also missing. And I think most of you don't get what ryanlath means: Sometimes it's just a waste of time to create special "folder" templates just to structure the information in the page tree (especially if they need different icons to distinguish them easier). It would be great to have some sort of pre defined "folder" or "strucure" element that doesn't (necessarily) create an url-slug. Example: I always create a template called "folder" (sometimes even 10+ just for the icons) and on the root of the page tree there are 2 or 3 folders like "meta" (containing legal information, contact...), Data (containing PageTable items), [...]. Those folders wouldn't need their own url-slug but i don't want their contents to "mess up" my page tree. This is just a matter of keeping things easy to navigate (in the backend) rather than grouping information in a semantic way.

I had the same issue with ProcessDatabaseBackups. See the related github issue: https://github.com/NicoKnoll/MarkupSEO/issues/4

Very nice looking site and well explained workflow. Is there any reason you didn't use something like isotope for handling the block grid? I already used it in a lot of projects and it works pretty good for those kind of layouts.

Very nice site. Also nice to see people using TemplateDataProviders and TemplateTwigReplace. If you've got any suggestions on improving the modules let me know. If you got questions concerning elasticsearch: We're just about to release a website which makes use of elasticsearch and modified ElasticSearchProcessWire quite a bit to fit our needs. It's really easy once you got into it.

First of all: Thanks for your help! I've just merged the pull request and altered some stuff. Basically I removed the part where you overwrite the fuel every time something is set. If it would have stayed like this you wouldn't have been able to overwrite fuel variables once they are set (no matter if they are proteced or not). Now all "system" keys are stored during module initialization and the setter method checks against those. Furthermore I replaced the isset() check within the getter with is_null as isset always returned false.

That's great and will surely become handy soon. May i suggest namespacing the css classes? Item, Facebook or Twitter are classnames that are potentially already beeing used across several frameworks and applications.

I officially claim this to be a comic sans day: One of those days git hates me and i hate git. // pushed another updated to github. this time it actually contains updates to the code.

I've just pushed a bugfix to github. The $ignoredTemplates variable wasn't populated when updating the module.

Yeah - you're right. That's why I've added the second option. I'll look into this issue asap. It was working in my test setup. I must have missed something.

TemplateTwigReplace TemplateDataProviders Database Backups FieldTypeCropImage FieldtypeTable / FieldtypeTableExtended

*shameless plug* We're using TemplateDataProviders for exactly this kind of jobs (preparing data before it's rendered). Maybe you should try it out, too. In your case I'd use output buffer and store it inside a variable to output it using twig later on. dataproviders/ContactPage.php <?php class ContactPage extends \nw\DataProviders\PageDataProvider { public function populate() { $modules = wire('modules'); $templates = wire('templates'); $form = $modules->get('FormTemplateProcessor'); $form->template = $templates->get('my_contact_form_template'); // required $form->requiredFields = array('fullname', 'email'); $form->email = 'your@email.com'; // optional, sends form as email $form->parent = $page; // optional, saves form as page ob_start(); echo $form->render(); // draw form or process submitted form $this->formMarkup = ob_get_contents(); ob_end_clean(); } } contact.twig {{ formMarkup }} Alternately you could add the Form Object to the templates namespace and render it directly using the method call within twig: dataproviders/ContactPage.php class ContactPage extends \nw\DataProviders\PageDataProvider { public function populate() { $modules = wire('modules'); $templates = wire('templates'); $form = $modules->get('FormTemplateProcessor'); $form->template = $templates->get('my_contact_form_template'); // required $form->requiredFields = array('fullname', 'email'); $form->email = 'your@email.com'; // optional, sends form as email $form->parent = $page; // optional, saves form as page $this->contactForm = $form; } } contact.twig {{ contactForm.render() }}

You're missing some quotation there. Take a Look at the altered Sourcecode in your post (the "$summary" part).

+2,5

Hi Bea, thanks a lot. I did see that the rendering didn't support the 2.5 attach/prepend settings but didn't have the time to implement it. I've merged your pull-request (and restored the indention to tabs !!!). Furthermore I've added a new config setting that lets you exclude templates from beeing rendered with twig. This is needed if you're using FormBuilder (and i can think of some more use cases).

This is great. I thought about doing a contact form module myself as i would have needed it in nearly every single project we've done recently. Btw: I like that all of your modules support TemplateTwigReplace!

The controls work fine for me. They just change to a paging-style navigation instead of arrows. Which browser/OS are you using?

Favicon is now included and the minimal-ui setting removed.

Yup. It was a problem with the apache vhosts :/ You're right. It's hard to read. I'll check if we can adjust the transparency or add some text shadow to make it more readable. Yup: sgh is operating internationally so there will be an english version in the future. Btw: Thanks for all your feedbacks. They're really helpful! Edit: Hey totoff, The "boxiness" is part of their corporate design. I think it's a matter of taste rather than an issue. I personally like it a lot though it has some drawbacks when doing a responsive design (same/fixed height & width boxes are really hard to implement in the way they are used within the site as the content needs to always fit in because you aren't allowed to vertically expand the box). Webdesign as a business is getting harder and harder as you need clients who understand it's not enough (for them) to buy a (mostly awesome looking) wordpress template for 50 bucks. I don't think "Webdesign" is a dying profession but it's shifting from developing "websites" to developing app like information systems that are device and context agnostic. I really like the direction Mozilla is going with it's Firefox OS and it's freshly released developer browser and hope the "web vs. native war" will get more equal as web technologies like webrtc, webaudio, webgl, ecmascript 6[...] evolve and are well supported across all devices. In my opinion it would be a big loss if the openness of the web is interchanged with closed ecosystems like apples or microsofts. But this is propably worth it's own thread

Thank you! I'll ask the next customer if we can do an ugly site for them. I'm sure they gonna agree. Will keep you updated!

This is caused by the "minimal-ui" viewport setting. You're propably right that it'd be better to remove it as the purpose of this setting is hiding the chrome for webapps or pages loaded within webview.

Ok. I think it's *really* fixed now. Sorry for the inconvenience (: