Jump to content

Guy Incognito

  • Content Count

  • Joined

  • Last visited

Community Reputation

32 Excellent

About Guy Incognito

  • Rank
    Full Member

Profile Information

  • Location
    Kent, UK

Recent Profile Visitors

502 profile views
  1. Fully didn’t know about this method - really useful thanks.
  2. Perfect thanks - so simple!... I had tried basically every combo of conditionals and was beginning to think it wouldn't work!
  3. Pretty much as the title - does anyone have a snazzy way to make a field that doesn't yet have any content front-end editable? Currently, the field cannot be double-clicked if empty but I would like to give users the ability to add missing content to a few specific fields.
  4. ha - great work on this - love the PW community! 😄 I've tried dropping your branch of the module into one of the affected sites but it doesn't seem to have fixed it 😕. Bit puzzled, as I'm almost certain things were working fine on all these sites previously.
  5. I'm guessing the main repo as we usually install via the CMS module installer. Does this sound like something that has already been addressed then?
  6. Hi all, we've started experiencing an odd problem where this extension has stopped auto-injecting the meta tags into some sites. The manual tag insertion still works. I can't work out the common denominator - has anyone else experienced this?
  7. Thanks to everyone who was helping me the other night. A little update on what I ended up doing with my helper module so far.... For the site settings, I ended up just making a configurable module with only one field containing a load of defaults stored as a simple JSON array. I thought this would be far easier for my specific purpose as it means that it's easily customisable with new data on a site-by-site basis without having to update the module interface or add new fields. I've hooked the $page object to access this data on the front end, so I can now do <?=$page->siteSettings['company_name'];?> etc in my templates which is cool. I've also set some dependencies in the config for the modules we regularly use. I have also used a hook to inject an overlay 'edit mode' icon that displays on the front end whenever an editor is logged into the site, as we've found some people don't realise when they're logged in and can use the front-end editing on their site. The little cog icon also links back to the PW dashboard. Really starting to get the hang of how the PW modules work now, so will be adding in lots more useful stuff we tend to use for every project in due course. 🙂
  8. Just came across this thread - for those who were wondering, we switched from ServerPilot to RunCloud + Linode for many PW projects and find it to be a great setup. Their support is great too, they’re in the Far East but always respond very quickly, not that we’ve had many issues. Very favourable pricing too compared to ServerPilot and way more features.
  9. Thanks 🤗 PW is also helping my coding get better - I'm mainly frontend, but it makes a great framework to safely grow my skillset and also have to rely on other members of my team less 🙂 I'll check out Kickstart - looks awesome. Yes - I've loved the template and dev work created so far with PW so having fun so far just experimenting to see what's possible with modules too.
  10. Yes to date I’ve been using a combo of pages and my own include files within the templates folder which works ok, just experimenting with the options 😁 My only hang up with profiles is how do you update them once installed. Whereas a module is easily updated across multiple sites. If I’m right, you can use a module to add pages and fields? If so maybe I need to switch my strategy for the module and do this instead of config fields.
  11. Ok thanks that makes sense why it doesn’t work. I do normally store this stuff in a standard page, but was using it as an exercise to dip my toe into modules as haven’t touched that element of PW yet. I just thought it might be cool to be able to install the module into each project without having to set up the fields etc.
  12. I'm teaching myself about PW module development by creating a simple module to hold frequently used settings for web design projects. I' ve set up a module with a config file to define a form with my settings fields. @ryan's tutorial here https://processwire.com/blog/posts/new-module-configuration-options/ says you can use "any Inputfield module name" - but image field gives me an error is an image field possible? "Error: Uncaught Error: Call to a member function path() on string in /home/testproject/public_html/wire/modules/Inputfield/InputfieldFile/InputfieldFile.module:913" Example array so far below - am I missing some confiuration values? array( 'name' => 'logo', 'label' => 'Logo', 'type' => 'file', 'value' => '', 'maxFiles' => 1, ),
  13. I'm still fairly new here having switched to using ProcessWire for pretty much every project (hence the frequent questions 😂 ) from Concrete5. Concrete5 has had Gutenberg-esque block-based front-end editing for nearly 10 years longer than Wordpress. Although a finished site using C5 can look great for a site editor/frontend-only user with various drag-drop layout tools, we were finding c5 development had become very convoluted and was starting to make simple website projects unnecessarily complicated. C5's core weighs in at a hefty filesize too. This is why we started researching for alternatives and landed happily at ProcessWire. I already find WP development unnecessarily convoluted, especially compared to the simplicity of ProcessWire. And with Gutenberg, I can only foresee the same sort of headaches ahead for the WP community that we were finding with C5 - namely conflicts between blocks and the core and frontend UI and your design style and functionality being dictated to by the CMS in order to work in the Gutenberg features. Discovering ProcessWire has been a revelation for us - the clean API and design agnostic approach are making everything from simple website projects to complex web apps a breeze, with the added bonus of super simple frontend editing that not only wows client's used to site builder platforms but requires basically zero onboarding too. I would urge anyone thinking of building out Gutenberg inspired modules for ProcessWire to consider the above comments to ensure that what makes ProcessWire special is retained.
  14. I agree - or just assuming if you are dragging over a page that it needs highlighting/opening.
  15. Sorry to bump an old thread but 3 years since you posted this just saved my day! I wonder if there's a way this could be made more obvious in the dashboard UI?
  • Create New...