Jump to content

wbmnfktr

Members
  • Content Count

    873
  • Joined

  • Days Won

    16

Everything posted by wbmnfktr

  1. 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.
  2. 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.
  3. wbmnfktr

    SeoMaestro

    Place the ready.php into /site/ and it should work. /site/ready.php
  4. 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.
  5. 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>
  6. 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/
  7. 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.
  8. 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
  9. 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.
  10. $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?
  11. In a local environment like Laragon you have to enable mail-catcher or an external SMTP. In case of MAMP there may be similar settings. With a local Linux environment you most likely will need sendmail, msmtp or a similar setup. When this happens on a regular hosting plan your provider might have disabled this feature. I'd recommend a look at WireMail: SMTP as it uses an external SMTP server/mail account (which you define). I'd say it's the most reliable way to send emails from within ProcessWire. But that's just my opinion.
  12. I loved doing that. Especially with my own projects. No matter how long they have been online. 2 years or 2 weeks. The slightest change and I started a rebuild. I try to stop this behaviour as it costs too much time. In case of a client project there is most of the time neither the money, nor the time for going this way. But... yeah, starting with a fresh copy is always great.
  13. You will remember it the next time. 😉 I checked the multilanguage support... that worked as well. As said before... try taking it apart with just a few simple templates to find the real problem.
  14. I tried this: fresh 3.0.123 installation multilanguage profile PHP 7.2 latest Pages2PDF module At first I saw no changes at all because I changed the wrong templates in /site/modules/Pages2PDF/default_templates/ and not those in /site/templates/pages2pdf/. Right now... all I can say is: it's working as expected. Sure... there is no custom code in my page templates or anythings. Just the basic stuff. My recommendation: try it with a simple basic template without anything else in it. Maybe even blindtext. Maybe the reason for your errors are at a different place than the module itself. Update: just saw in your post that you ARE in the wrong folder with the wrong templates.
  15. Just to get the records straight... ProcessWire version? Multilanguage profile or another profile made multilanguage? How many languages? Does it work in any of the languages? PHP version? Module version? How do you generate the PDFs? Code snippet would be great Where do you create the PDFs - frontend or backend? Templates: page or PDF? Template location? Template strategy - delayed, direct, regions?
  16. I maintain a 2.5 instance of ProcessWire which needs to be upgraded in the future, too. Not only ProcessWire itself but design and functionality as well. 1.) My first test-run showed me that several things changed. The biggest issue so far was a field called limit. It worked in that site but with 3.x it doesn't. Some names are not allowed anymore - or are already pre-defined somewhere but there are easy ways to avoid that. Just rename those fields before upgrading. Which brings us to the next point. 2.) Always use a test instance and have a working backup. 😉 3.) Modules are a big roadblock. Some don't work anymore with 3.x, some just say they don't support 3.x and others just need to be updated. By now I downloaded the most recent version of all modules manually. Switched old modules for newer ones and changed the ProcessWire core at the same time. It worked pretty well - after hitting refresh a few times. 😎 4.) Compiled files cache, markup cache, sessions... just drop them. At least that's what worked for me. 5.) Crawl the whole site after first upgrades to find 3xx, 4xx, 5xx issues - I use ScreamingFrog and the Jumplinks module. 6.) Namespace... I had to add it to some files. 7.) I created a site profile from my upgraded copy and tried to install it. Just to check if everythings works even after exporting it and such things. It worked. Luckily. So I had a first, clean. updated and working version of that project for the upcoming changes.
  17. Just in case - don't activate the auto-accept option. Unless you modified the code to auto-disable cookies.
  18. As you allow users to manage their decision/choice change one line in your module and it's done. notice.tpl.php - Line 18 <span class="pwcmb-widget__close js-pwcmb-manage-cookies">Close</span> Instead of accepting cookies the user has to choose now wether he allows or denies cookies.
  19. We could call it a marker of some kind. Yes. And everything around it. As said... install it and play around. There are tons of things you can change, edit and do with it. Depending on the tools, cookies and things you want to use, you might want to extend parts of the module with your logic and functions.
  20. First things first. Look into your field settings if there is a (new) limit set and also check your php.info for these two option: upload_max_filesize = 20M post_max_size = 20M
  21. Are all your modules up to date and compatible with ProcessWire 3.x? You can clear the compiled files cache - can be found at the bottom of your module page - and try again.
  22. The module itself is more like a toolkit. It looks for a cookie to show/hide the banner and sets value(s) depending on the user's choice and your settings. Based on that decision and your settings you can build up your more complex logic if needed. if(localStorage.getItem('pwcmbAllowCookies') == 'y') Source: http://modules.processwire.com/modules/cookie-management-banner/ That snippet allows you to trigger/load Matomo, Google Analytics, Tag Manager, Amazon, whatever. Play around with the module and keep an eye on all the cookies/localStorage values and when they get set. So... coming back to your question: if the user neither allows, nor denies cookies the module does almost nothing. There is an option to autofire/allow cookies/track visitors but at the end you always decide what happens in which case. You could build something like this: https://github.com/webmanufaktur/CookieManagementBanner/blob/master/assets/html/CookieManagementBanner.OptInOut.html
  23. Sounds like you could use LazyCron here. Check your pages how often you want (daily, weekly, each hour), look for those pages and do what ever you want to do with them. Put things like this in ready.php or create a module: <?php namespace ProcessWire; wire()->addHookAfter('LazyCron::every6Hours', function (HookEvent $e) { $pagesOlderThirtyDays = $e->pages->findMany("template=order, ... "); foreach ($pagesOlderThirtyDays as $potd) { // WHATEVER YOU WANT }; });
  24. Just queried Google and there might be a problem with either ImageMagick Ghostscript Missing fonts Wrong/false/incomplete embedded fonts Other font issues Or in short... if it's a server-related you might have to dig quite deep into it. From ImageMagick versions to installed Ghostscript fonts to (above mentioned) policy restrictions. Depending on your hosting or the client's hosting it might not even work. Shared hosting plans don't allow access to files and folders - but in most cases those environments are pretty well configured. It might be easier to create a already pre-rendered first page for the PDF without any real text and fonts. Maybe converting them to paths or however it works in InDesign. As it is only a download and nothing you'd push to a print shop, it should work out just fine.
×
×
  • Create New...