Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by PWaddict

  1. Thanks and sorry for not responding sooner but on the last months I've been busy with other stuff. By the time I will I finish those you will probably already have the website, demos etc. ready. Btw, will you brink back the padloper.pw or the new Padloper "website" will be on processwireshop.pw?
  2. Thanks for the reply. You know better how to price your own product but I'm not talking about that. As I'm a Padloper 1 owner it would be really helpful if I knew what Padloper 2 has to offer me that Padloper 1 don't, in order to help me decide if it's worth investing on it since there is no upgrade option with an "attractive discount" as you originally planned (btw, that would probably be an instant upgrade πŸ™‚) Since we agree to disagree, I will wait for the new Padloper website to check all features, demo videos etc...
  3. Hey guys, Has anyone built a multi vendor marketplace with ProcessWire? Did you used Padloper and Login Register Pro too? On the e-commerce section of the ProcessWire sites showcase I didn't find any marketplace there. If you know any multi vendor marketplace powered by ProcessWire please share a link via pm. I would really like to see it in action. Thanks.
  4. Congrats on releasing Padloper 2 πŸ™‚ Can you show us a feature comparison list between Padloper 1 & 2? I'm Padloper 1 (dev) owner and I would like to know if it's really worth paying x6 the price of the first version. Thanks in advance.
  5. @sms77io Is it possible to send sms via PW API?
  6. Yes, I'm 100% sure. ProcessWire has 2 properties for cache-busting, URL & HTTPURL. Taken from https://processwire.com/api/ref/pageimage/: HTTPURL string Same as the cache-busting uppercase β€œURL” property, but includes scheme and hostname. URL string Same as $url property but with browser cache busting query string appended. Taken from https://processwire.com/blog/posts/pw-3.0.98-procache-buster/: ProcessWire's file and image fields (represented by Pagefile and Pageimage objects) already have an uppercase URL property which always returns a cache-busting version of the file's URL. This is the case whether you've got ProCache installed or not. But in ProcessWire master 3.0.96 or newer, ProCache Buster updates that URL property to use ProCache's enhanced buster, rather than the one built-in to the core.
  7. @Mike Rockett can you please change only 1 word in order to enable cache busting image urls? On the file SupportsImages.php at the line 28 change the httpUrl to uppercase: HTTPURL $locImage = new Image($image->HTTPURL); With this change you will support both PW core's and ProCache cache busting.
  8. I know, already edited / added pages that contain a CI field but I keep getting the notice.
  9. Hey, guys! Did you find any solution? I keep getting: Modules: Detected 1 module version change (will be applied the next time each module is loaded): CroppableImage3: 1.1.16 => 1.2.0
  10. @teppo I have on Laragon some older PHP versions installed and did some tests: PHP 7.033 = Still getting the notice PHP 5.6.40 = NO notice So this is definitely a PHP 7 compatibility issue.
  11. I guess you have to switch to 7.4.x to actually get the notice. I'm using the PW master version 3.0.165 and the 1.3.1 of Version Control. It happens only on the pages where I have enabled Version Control. I tested it also on a brand new PW installation where only Padloper module installed and I'm getting the same notice on the php_errors.log.
  12. @teppo Thank you very much for this module. I have enable version control on some fields at the user template. I'm using PHP 7.4.9 and when I visit a user page I'm getting this PHP Notice: Trying to access array offset on value of type int in C:\laragon\www\mysite\wire\core\WireDatabasePDOStatement.php on line 107
  13. @strandoo Thank you for sharing your solution. It works perfect πŸ™‚
  14. Hi @flydev πŸ‘ŠπŸ» I just installed the module and I'm getting this PHP Notice: Notice: Undefined index: data_badge in C:\laragon\www\mysite\site\assets\cache\FileCompiler\site\modules\MarkupGoogleRecaptcha\MarkupGoogleRecaptcha.module on line 269 Replacing the 269 line with this, fixes the issue: if(isset($data['data_badge'])) $f->attr('value', $data['data_badge']);
  15. Hi, Has anyone integrate reCAPTCHA?
  16. This is years ago. According to the comments, back then it was working fine for superusers but unfortunately not now. I'm using the master version 3.0.165 and as superuser it doesn't work.
  17. Hi, I have created a "Page Reference" field and on the "Input field type" I selected "Page Auto Complete" under "Single page selection". Then on the selector string added: template=user, roles=login-register, sort=name I'm not getting any results when I start typing the user names on the page field. If on the "Input field type" I select "Select" under "Single page selection" then it works fine. I can see all the users. Why it doesn't work with "Page Auto Complete"? I want this for me as superuser.
  18. Yep, problem is gone. Thank you very much.
  19. Here are the settings for the repeater: Here are the settings (Details & Input) for the image field (Croppable Image 3): Here are the settings for Custom Upload Names: I don't know if it matters but here are the settings for Auto Smush: Make sure you have the 1.3.1 version installed of Custom Upload Names. The fatal error is happening if you try to edit already published more than 1 repeater pages and also when you try to create more than 1 new repeater pages.
  20. This was in a non-repeater. The duplicated images were generated on the 1.2.11 and 1.2.12 versions after uploading multiple images. I don't know if this happens on repeater too. The fatal error I'm getting with the 1.3.1 version is when I try to save more than 1 repeater fields. I didn't have problems on non-repeaters. No worries.
  21. Actually, I had to switched to an even older version 1.2.10 (24 Nov 2020) cause the 1.2.11 and 1.2.12 was generating duplicate images. The 1.2.10 is the most reliable version so I'm gonna stay with it until the 1.3.1 gets fixed.
  22. I switched to this version (18 Feb 2021) and I can save more than 1 repeater fields without any issues.
  23. Hi @adrian With the 1.3.1 version when I try to save more than 1 repeater fields I'm getting this: Look out… Fatal Error: Uncaught Error: Call to a member function isTemp() on null in site/modules/ProcessCustomUploadNames/ProcessCustomUploadNames.module.php:414 #0 site/modules/ProcessCustomUploadNames/ProcessCustomUploadNames.module.php(225): ProcessCustomUploadNames->createNewFilename('/home/myusername...', 'myimage-16198119...', '', Object(Page), '287', Object(RepeaterPage)) #1 wire/core/Wire.php (397): ProcessCustomUploadNames->customRenameUploads(Object(HookEvent)) #2 wire/core/WireHooks.php (927): Wire->_callMethod('customRenameUpl...', Array) #3 wire/core/Wire.php (465): WireHooks->runHooks(Object(Pages), 'saved', Array) #4 wire/core/PagesEditor.php (746): Wire->__call('saved', Array) #5 /home/myusername/publ (line 414 of site/modules/ProcessCustomUploadNames/ProcessCustomUploadNames.module.php)
  24. Thanks for the hint @elabx Your code makes ALL options fields available in the Lister columns to display the same values. Here is how I did it: $wire->addHookAfter('FieldtypeOptions::markupValue', function($event) { if($this->process != 'ProcessPageLister') return; $field = $event->arguments(1); $value = $event->arguments(2); if($field == "my_options_field") { $event->return = $value->value; } });
  25. Hi. I would like to display on the lister the values instead of the titles from a specific options field. Can anyone please help with the hook?
  • Create New...