Jump to content


  • Content Count

  • Joined

  • Days Won


Everything posted by wbmnfktr

  1. Running into this issue right now with a quite large site I look into for performance reasons. Installation was quite tricky with a 420 MB database, lots of template, fields and even more pages. Anyone any idea how to fix this or where to look first?
  2. Just threw some wallpapers at it and... well... really like the result so far. Great tip!
  3. wbmnfktr


    There is still Theme Forest and some other good commercial sites. In case of commercial themes you have to read through the license agreements carefully if you plan to provide the site profile afterwards or in case of free themes you want to ask the creator first.
  4. Can't wait to get my hands dirty with the upcoming FormBuilder v40. But there is one thing I'm asking myself now: How about saving those re-used forms into pages? Will there be still the need for all kinds of fields for templates?
  5. Those are? It's in the cookie. Saving it server-side would open even more gates therefore some solutions are not GDPR-safe as they save it on their servers. Where is that quote from? By now I have a solution on some of my personal projects that are approved by lawyers to be GDPR-safe and those could collect tons of data... just by one cookie and one click. I paid lots of money to be safe ... so your sources would be really nice as I could get some money back - maybe.
  6. After each session? I really doubt it but where did you get this info? Didn't find that session thing on eRecht24, WBS, JanoLaw and others. I source for that would be awesome! If that's the case some parts of the module/script need some changes to reduce cookie lifetime. Right now the cookies live quite a long time - as the user opted-in or out.
  7. So... I installed it and... maybe @ryan wants to take a closer look at it. I don't know if this is correct in any way. Maybe it's both at the same time... somehow. Don't know.
  8. That module is listed in every ProcessWire installation. Screenshot below is from an instance I installed a few days ago. So... I guess they don't ship Pro modules with it.
  9. Well... actually... that theme is based on ProcessWire and comes with a full site profile so the question wasn't that wrong here. They say: Quick install in less than 5 minutes (Using Processwire wizard) Powerfull admin panel (Processwire) that makes sense for both the developer & client Helpful documentation + Processwire documentation That's the first commercial ProcessWire theme or profile I have seen in the wild.
  10. If you have Site Profile Exporter installed I'd create an export next weekend.
  11. Don't know anything about them - at least I can't remember it. That's far from best practice - I would try another solution here. Sure... would be nice to tinker with it but it's hard to tell what to do first without any insight. Is there a repository or profile export I could checkout or even install locally?
  12. You might want to consider Cloudflare as a CDN and kind of protection layer for your site. They block spammy requests, cache what's possible and can give some control over what's happening. But please read through the GDPR things before. Maybe it's time to clean up the site a bit in order to have a much smaller footprint in terms of server connections, memory usage and page sizes. What kind of hosting is this? Are they reliable?
  13. I like the 2 months free at skillshare deals way more. This offer feels already a bit off right from the start. Don't know why.
  14. Your database doesn't respond (in time) aka is down. Saw this quite often in uncached projects on cheap hosting plans. Why? Maybe too many open sessions or a too many requests in very short period of time. Look into /site/assets/sessions. If that folder if full with files it might be the cause of this issue.
  15. Maybe you will find something in the logs /site/assets/logs.
  16. Have you tried removing $p->of(false) ? Otherwise have a look here: https://processwire.com/docs/fields/repeaters/ Repeater fields need to be initialized in order to accept a new item. At least it was necessary in the past. Maybe that's the case why it doesn't work. $building = $page->buildings->getNew(); // initialize - the important part $building->title = 'One Atlantic Center'; $building->feet_high = 880; $building->num_floors = 50; $building->year_built = 1997; $building->save(); $page->buildings->add($building); $page->save();
  17. Some details were written down here: https://processwire.com/blog/posts/pw-3.0.139/#new-toggle-field This is some kind of feature you have to use, need or want to fully understand this fieldtype. I actually love to have such a field - but haven't played with it yet unfortunately - as it will probably save me tons of time and make things easier in the future. I will use it for conditional settings in my templates - I guess. At least I needed this kind of possibility in the past and now it's here.
  18. wbmnfktr


    Heads up: SeoMaestro and ProcessWire 3.0.139 (DEV) don't like each other. Just ran into this issue - luckily in a local testing environment - while creating/editing a SeoMaestro field. Fatal Error: Uncaught Error: Call to a member function prepend() on null in /home/alexander/www/ssw.test/wire/core/Fields.php:1066 Stack trace: #0 /home/alexander/www/ssw.test/wire/modules/Process/ProcessField/ProcessField.module(1412): ProcessWire\Fields->getCompatibleFieldtypes(Object(ProcessWire\Field)) #1 /home/alexander/www/ssw.test/wire/core/Wire.php(380): ProcessWire\ProcessField->___buildEditFormBasics() #2 /home/alexander/www/ssw.test/wire/core/WireHooks.php(813): ProcessWire\Wire->_callMethod('___buildEditFor...', Array) #3 /home/alexander/www/ssw.test/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\ProcessField), 'buildEditFormBa...', Array) #4 /home/alexander/www/ssw.test/wire/modules/Process/ProcessField/ProcessField.module(1020): ProcessWire\Wire->__call('buildEditFormBa...', Array) #5 /home/alexander/www/ssw.test/wire/core/Wire.php(380): ProcessWire\ProcessField->___buildEditForm() #6 /home/alexander/www/ssw.test/wire/core/WireHooks.php(813): ProcessWire\Wire->_callMethod('___bui (Zeile 1066 in /home/alexander/www/ssw.test/wire/core/Fields.php) Diese Fehlermeldung wurde angezeigt wegen: Sie sind als Superuser angemeldet. Fehler wurde protokolliert. Update: 3.0.140 same behaviour
  19. Never felt comfortable with CSS naming conventions like BEM... I tried a lot but never really used it from start to finish. My variable and/or class names are a wild, weird and colorful mix of everything. 😂 And I'm even guilty for things similar to this: .yet--another--color--change--experiment--123 {...} .the__client--asked__for--it {...} It's like eating healthy. I know how it's done but... 👼
  20. Just to let you know: Server directory option includes the ready.php here on my setup.
  21. Ok, this is a very good detail. I always use ZIPs as I push them - as they are - to the new system. I will try the Server Directory tomorrow and let you (all) know if this makes a difference here on my side.
  22. Can't confirm this. Just moved 2 sites/profiles from local to another instance. Neither of them had ready.php, init.php or finished.php in the created profile ZIPs.
  23. After a quick look into some projects I took more care about files: assets (/site/templates/assets) brand brand-company-logo.ext brand-company-og-image.ext favicon.ico (just a backup - the .ico always sits in the document root) favicon.png ... fonts plex proxima icons* (icons often end in my .css files - a ProCache option, therefore names don't matter here) whatever-123123.svg the-file-912321.svg was-named-or-4572.svg helps-me-to.svg find-the-icon.svg i-need.svg vendor jquery jquery-3.x.x.js slick z (storing things I don't need anymore without deleting them - just in case) * icons are in 99% of all cases just decoration elements so I use them very often as backgrounds and not as images. Every image that's not content on its own or part of the content will not end in an <img .../> tag. In case of gallery arrows I try to use text links/span-elements and re-style them with CSS. The icon itself will be in my CSS most of the time.
  24. After my post yesterday I realized that there is actually more I do. At first I thought I don't think that much about naming but then I looked into a recent project and found several patterns that seem to be part of my workflow for a while now but I never saw that as a naming convention to be honest. It's more my laziness. I hate searching around so I group templates and fields in some cases to make things easier for me - I guess. Templates for data that will never result in a viewable URL/page get the prefix data, for example: dataPerson dataWebsite dataProject dataProduct Then there are templates that result in real pages/URLs which get the prefix content, for example: contentPage contentPost contentEvent contentGallery Then there are templates for pages that result in real pages/URLs but don't contain real content on their own which get the prefix list, for example: listBlog listMovies listRecipes listTeams There are some more templates types but I'll skip them here as they are too much based on my workflow and projects - sometimes. "Yeah... but what do you do if a data template needs to be changed and a page should become viewable?" Well... I rename it, create or rename the .php file, do the things that are necessary to get the task done and I'm ready to go. While developing a project this can happen - but not that often actually. It's more often the case later on when the website owner decides to push more content into Google's index. As it is a client request I'm totally happy with it and can invoice my work. In terms of field names I go the way @teppo already mentioned but with a little twist at the end. I name the fields depending on their purpose. headline subline summary excerpt intro bodycopy images heroImage heroVideo videoYoutube videoVimeo urlFacebook urlTwitter urlLinkedin nameFirst nameLast nameFull You can see that I try to group fields by their name structure. Instead of firstName and lastName I reverse the order and these fields stay together in my list of fields. That makes life much easier in case I need to look up something or want to find out if there is already a field I can use. But... is this really a naming convention? I don't think so.
  25. My experience with this in the past: The more I thought about naming conventions the less files I created - therefore didn't get anything done. Cleaning up afterwards was sometimes a mess but at least I had something to clean up. If you are working in a team, talk about it and think about it together. If you work alone you will find your way somewhere in the future.
  • Create New...