Jump to content

wbmnfktr

Members
  • Content Count

    835
  • Joined

  • Days Won

    16

Everything posted by wbmnfktr

  1. I think you didn't run in this trap but just to mention it: test it with another browser and a real guest/visitor and not with the admin/superuser. Yes... enabling this by default should do the trick then.
  2. Ok... well... I don't know. There are only a few things and thoughts left so far. check what has changed in the last days/weeks since it broke maybe GD or ImageMagick (don't know if this exists in 2.5.x) are failing ask the hosting company if there were any changes (security efforts, file scanners, whatever) remove any restrictions on that field use another browser use another user check console for errors check disk space Last and final thought: Make a backup, test it locally and take it apart.
  3. Just a guess but I think this will work for already existing pages and files as well. I never used this feature for any of my projects - at least I can't remember so. Just give it a try in a dev environment on your local machine. Shouldn't take more than 30 minutes to get this up and running for a test ride. If I remember this correctly @Jens Martsch - dotnetic could answer this probably.
  4. What does the full error message say? Are there any permissions set in that field or template or user? Have you tried another image? How large is your image - MB and pixels? Can you switch to a more recent PHP version (your 5.6 seems a bit dusty)? Also check upload_max_filesize and post_max_size.
  5. It looks like you could use: $config->pagefileSecure More details here: https://processwire.com/api/ref/config/ and of course via search in the forum. 🙂
  6. First of all... thank you @adrian for the introduction and the great work with this module. In the last couple of days I created a DEV branch with some minor changes and fixes I found while testing the latest version (0.4.11). If you are interested in playing around with that version, grab a copy over at Github - the DEV branch is linked below. As always: backup your site and previous module first. All changes so far: FIXED: Vanilla JS version notice toggle didn't work when MANAGE disabled FIXED: Version change didn't trigger reset INFO: Added usage examples (assets/html) CHANGED: Removed CLOSE option ADDED: Datalayer details to README Issue tracking on Github was also enabled. This could make things easier in the future. Feel free to open an issue there whenever you find a bug. Don't forget to add the obvious details (ProcessWire version, PHP version, expected behaviour, your module settings and custom code). DEV-Branch https://github.com/webmanufaktur/CookieManagementBanner/tree/dev Issues https://github.com/webmanufaktur/CookieManagementBanner/issues
  7. As you can read in the previous posts there are some issues with the module right now. There haven't been any updates so far in the official repository. So you might have to dig through errors and fix them. Right now I wouldn't recommend this module in any project unless you want to take care of all possible issues. What's the main feature you are looking for? There are several other modules out there so maybe we can find a solution for your needs.
  8. I don't know what it was in my case but one of these things fixed it or at least I got the .png files in my PDFs: using relative path to the file installing GD and PHP GD extension (or was it ImageMagick?) And somehow I was able to get more details about the problems aka got a real error message but it's way too long ago as I can remember this in full detail.
  9. I'm around here for a while now but never saw this until now. It's awesome. Why is watching this not mandatory in some kind? 😂
  10. Do you develop on your local machine or on a remote server? Maybe your problem is similar to this one - if you are working on a remote server: And you have to disable - for the time you update and develop - some security features aka fingerprinting.
  11. A totally fresh installation or new try/rework of your existing site? If it's not a fresh installation you could try this: delete session files /site/assets/sessions delete cached/compiled files in site/assets/cache/FileCompiler Check if both instances - old and new - have the same userAuthSalt value in their config.php.
  12. wbmnfktr

    403 Error

    Well... to be honest... your screenshot doesn't make sense. On the left is your user's home folder. Which isn't meant to be a home for a website at all. Therefore all .php files in there are totally wrong there, while .xsession and similar files are needed there there. On the right is probably your hosting/server. But there is everything mixed up. Again. If that that folder is your domains document_root than there are some folders missing and some files at totally wrong places. That's how a ProcessWire folder in the document_root of a domain should look like. At least these are the files I would assume there.
  13. From my experience: Jumplinks and ProCache play really nice together.
  14. Ok. I don't know if there is anything modified in your site or a difference in our installed modules so this might not work but I just installed ProcessBlog & MarkupBlog and of course the latest Jumplinks module. I unpublished the example post, opened it in a private window where a 404 showed up. I looked into the Jumplinks 404 monitor and found the request. I opened that entry, created a new jumplink from it and visited the URL in a private window again and... it worked. ProcessWire 3.0.123 the other modules straight from modules.processwire.com.
  15. Are those domain.test/blog/post/ URLs based on URL segments in the template? If so... that might be the reason why JumpLinks doesn't kick in. It's not a solution but maybe another thing you could look into.
  16. To be honest... don't do it on a remote machine. Install Laragon, MAMP or something similar on your local machine and play around with ProcessWire. I personally prefer the blank profile but in your case the beginner profile shoud be perfect. Combined with the ProcessWire tutorials you will have a solid foundation for a perfect start in the world of ProcessWire. Depending on your skillset and experience with PHP and maybe other CMSs you could be ready to build your very first site in/with ProcessWire on Monday next week.
  17. These threads discuss similar issues: While developing you might want to disable fingerprinting from within config.php - it's explained and discussed in the threads above. Another thing you can and might want to doublecheck: CDNs can be sometimes an issue as well; saw this with Cloudflare CDN a few times some browser extensions (privacy and adblock-related ones) can cause those issues as well Pi-Hole can be an issue too Operas built-in-VPN causes these conflicts/problems (especially in tools like Asana and Slack - and PW) And those things are just the few I remembered from similar situations I had to deal with on my own.
  18. wbmnfktr

    SeoMaestro

    Place the ready.php into /site/ and it should work. /site/ready.php
  19. Hard to tell why this isn't working as expected without knowing about the whole setup and your templates. Either the template doesn't contain any code to show the description or the site is cached. Who built that site? Maybe they can take a look into it. We can almost only guess.
  20. What about this: <div class="masthead" data-bg="<?php echo $page->mastheadImage->url; ?>"> <span>My Text Above Image</span> </div> and this: <script> $(document).ready(function() { $('[data-bg]').each(function() { $(this).css('background-image', 'url(' + $(this).attr('data-bg') + ')'); }); }); </script>
  21. In 3.0.137 a new version of CKeditor was added. Maybe that's the reason. https://processwire.com/blog/posts/pw-3.0.137/
  22. PWImage is enabled by default and the button itself is present by default as well. But it's only available in textarea fields and not text fields and you want to add an image field to your template as well. That makes things easier.
  23. So you want to send a copy to the website visitor itself? Never tried it but... you can define additional recipients within the options and maybe even from within a hook. <?php $this->addHookBefore('SimpleContactForm::sendAdditionalMail', function(HookEvent $event) { $form = $event->arguments(0); $emailCopy = $form->get('scf_emailcopy'); // more logic here }); More details and another hook example at the bottom of the page: https://github.com/justb3a/processwire-simplecontactform
  24. You wouldn't. Just use $image->description as it's the actual image which has a description. Your thumb and large variations or just that. Variations of the original image.
  25. $content .= "<a href='$large->url' class='thumb-roll'> <img src='$thumb->url' alt='$image->description' /></a>"; How does your code before that part looks like? I guess you already tried $large->description and $thumb->description. Correct? Are descriptions set?
×
×
  • Create New...