Leaderboard
Popular Content
Showing content with the highest reputation on 06/02/2019 in all areas
-
The functions api is not multi instance aware anyways, so you cannot use it in `site2` anyways. If you disable it via the config the error should go away.3 points
-
So I started off with your suggestion @elabx, but I'd forgotten my field is actually a multiplier, not just a straightforward text field. After messing around with it for a while I gave up. I couldn't even get it to look into the array and pull out the first one. While your suggestion sounds very cool @Autofahrn it's a bit beyond me at this stage. Maybe one day I'll have the confidence to go there...! ? In the end I used RuntimeMarkup (thanks @kongondo - especially for going to all that effort to set up a trial account!), but in a very basic way. I've just used it to do what I would've done with the method suggested by @elabx if I could've figured out how to correctly hook the multiplier. The end result is I now have a nice little thumbnail preview of the first specified image showing on my edit screen, which is all I really need at this point. Later on I might look at putting in something a little more advanced. Thanks once again to all of you. ?3 points
-
ANOTHER UPDATE SnipWires Taxes (VAT) configurator is ready! I added a new custom Fieldtype FieldtypeSnipWireTaxSelector based on an idea of @BitPoet - thanks for that! Also I created a full featured repeater for module config editor including drag&drop handling. Have a look at the animated GIF below. The taxes you configure here will be available as select option list in product page editor. The first tax in the configured list will be used a s the default tax in the custom field.
2 points -
UPDATE OK, after I've faced that for and against again, I've decided to make the module freely available. If you are interested, you can test the current state of development. I already put the module on GitHub. Please note that the software is not yet intended for use in a production system. (Alpha version). For example, the configuration and handling of the VAT rates are still missing. Also the dashboard is still incomplete. And many other things needs to be improved and implemented... ? If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests. https://github.com/gadgetto/SnipWire2 points
-
This week we’ll take a look at 3 different WEBP image strategies that you can use in ProcessWire 3.0.132+. Then we’ll dive into a major update for the Google Client API module, and finish up by outlining some useful new updates in FormBuilder— https://processwire.com/blog/posts/webp-images-and-more/1 point
-
1 point
-
I have the same problem - I think it is caused by some email clients placing <style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style> inside a <head> tag. Something then deletes the <style> tag. The culprits could be any of: this module HTMLpurifier for the textarea field CKeditor Unfortunately, I have not been able to replicate it with my email client, so checking where the problem is has been tricky. I think that it is most likely (1) or (3) or both. To eliminate (3), place style{display} in the CKeditor "extra allowed content" of your textarea field (input tab). If it still happens, you could try hacking lines 511 and 514 of ProcesEmailToPage.module to include <style> in the list of allowed tags. Let me know the results, Ta. UPDATE: Hi @cstevensjrI managed to create a test email using gmail and developer tools. I think you need to fix both 1 & 3 as per my suggestion. You will see from my previous post that I have suggested a module change to avoid trapping tags like this.1 point
-
Oh my goodness, thanks to all of you for your responses. I'll sit down and take a proper look tonight and let you know how I go. This community is so awesome! ?1 point
-
I just released version 0.7.0 of the module: It fixes the ugly label being showed above the "inhterit" checkbox for newer Processwire versions. I think there is a bug in core, because ProcessWire ignores the fact that the label is marked as "hidden". I had to fix it via CSS for now. Added the possibility to resize the Opengraph image when referencing a page image by specifying a width and/or height. Opengraph image: If the referenced image field is empty and pulls the image from another page (default value), the module now substitutes the default image as well. Other than that the readme now contains a chapter for the various hooks provided by SeoMaestro. This might be interesting if you need to customize the behaviour of the module. Please let me know if you find any issues! ? Cheers1 point
-
A more complex approach would be a new fieldtype which allow to browse and select through the SmugMug API. Edit: just found this, which may help to go that way: http://phpsmug.com/1 point
-
The most simple approach I can think of right now is hook into after InputfieldText::render: Put this code in site/ready.php: $wire->addHookAfter("InputfieldText::render", function($event){ $field = $event->object; if($field->name == "text_field_name" && $field->value){ $markup = $event->return; $url = "https://somedomain.com"; $markup .= "<img width='100' src='". $url . $field->value ."'>"; $event->return = $markup; } }); I'm assuming $url is whatever you need to append to complete the url with the ID in place. This should render the image right below the text input. If you want to dig a bit more, check the code in the link I pasted and debug with a $log->save() the $markup variable which basically gets it's content from the $event->return property which matches the return value of the render function in the Inpufield code.1 point
-
Hmm... I think the sanitizer itself works as you say. There's something else interfering which I don't understand. For info, my use case is to distribute emails from committee members to other committee members and keep a central repository, so there are several steps in the process - the module, email clients and PW core (plus my own code) - so finding the culprit is proving a bit tricky. The body field I am using has HTML Purifier enabled, so using it in the module doesn't really do anything (apart from seeming to add spurious <p> tags). As regards amendments to the module, on reflection, it seems that there are several possibilities for adding options: Further allowed tags Set stripTags =>false Use sanitize-purify rather than sanitize->textarea Don't sanitize (rely on host field sanitization) .. and maybe more. Given this, it might be best to wait and see what @Pete thinks.1 point
