horst

https://www.i-programmer.info/news/197/12978.html Nothing practical for me, but an interesting read. ;-)

Tracy debugger has many tools to help in development. One of them is the user-switcher, which exactly does what you asked for! There are also other modules out there that provide this user switcher functionality. If I do remember right, @Pete has build and released one. (search in the modules directory for it) My ALIF module once came up with this, but in the meantime I have stripped it out, as there are now other solutions for this, so that I don't have to maintain to much functionality with my modules. :)

@ryan in regard of debug_backtrace(), I ask myself, if something like this, PHP String Hidden Characters: Hide strings to avoid appearing in stack traces, may be useful for us in some parts too? Thinking on names, emails, document_roots, serialnumbers (Promodules), etc., - as people tend to copy&paste their stack traces into (public) forum posts when asking for help.

Can you may use the IMagick-Engine instead of GD, just for testing? You can enable it under modules > core > image, if your server supports it.

Hi @Edison, if this shows the old and the new values inlog and mail, this is really good! (Will test this later when back in buero). Only thing that should be changed is the use of (PHP) @mail function. Instead you should use wireMail(). :)

@MoritzLost, I use the lastmodified timestamp of the css or js file as cachebusting value. This way the files gets reloaded when needed, but can be cached in dev and live sites.

@Markus (Blue Tomato) the showIf only works with fields and there values. AFAIK, the published / unpublished value cannot be used as condition for showIf directly in the template editor. But you may define a hook and set the visibility of that field within the hook. Here is example code as a starting point. You can use this in site/ready.php $wire->addHookAfter('ProcessPageEdit::buildForm', function (HookEvent $event) { // make sure we're editing a page and not a user if($event->process != 'ProcessPageEdit') return; // get page and form $page = $event->object->getPage(); $form = $event->return; // optionally check for matching template(s) with a condition if('mydesiredtemplatename' != $page->template->name) return; // get the field and conditionally set the visibility $form->get('yourfieldname')->collapsed = $page->isUnpublished() ? Inputfield::collapsedHidden : Inputfield::collapsedNo; $event->return = $form; return; }

Sorry, no. The current text watermark method analyzes the images and decides between white, gray and black in a automated way. The reason behind that is, you can apply text to any images without knowing which colors it includes.

@Macrura thanks for the hint. Have you tried to change that continue into break at line 525? Does it solve the Warning?

As I understand it, „I prefer“ is not equal with „I never do“ or „I always do“. A single decission may be a compromise related to: possibilities, „costs“, and possibly available manpower compared to expected time expenditure. ?

@tonicastillo Many thanks for sending me your images. I have tested with the original image on windows and on linux. My variations always had correct and 100% identical iptc metadata as the original has. (see my screenshot via PM). It seems you have to control which part within your workflow chain is not properly set to UTF-8. If you are using PW >= 3.0.132, you can use the following code to get direct debug output from images and variations: $image = $page->images->first(); // get the original image, (adapt to your needs!) //echo $image->getDebugInfo(); // THIS MUST BE OMMITTED, BECAUSE I FOUND SOME SORT OF "STATIC" BUG WITH THE NEW DEBUG-METHOD $options = ['forceNew' => true]; $variation = $image->width(300, $options); // create / recreate a (new) variation echo $variation->getDebugInfo($options); // debug output Parts you need to check can be the OS default charset and/or codepage, PWs php files, the Webserver DefaultCharset, etc. In the modules directory you can find a useful set of inspection tools: https://modules.processwire.com/modules/process-diagnostics/ that assists in some parts. It has diagnostics for PHP, Webserver, Filesystem, etc. -------------------- PS: Normally it should be possible to query debugInfo for multiple images one after each other, but an optimization error has crept in.

Hi @tonicastillo, I'm not sure, but it looks like something in your workflow is not utf-8 save. Can you send me one original (uploaded) image, where this happens? You can use PM or my email address, if you like: https://nogajski.de/contact/ Thanks.

You would ask with $pages->get(„yourfieldname=requiredvalue“), or with $pages->find() If you not allready have setup your tags field, you may look at the pagereference fieldtype, or the options fieldtype. Your selector to find pages with the requested flag may include specified templates, parent or others, to be more precise. And if you not allready know the differences between get and find, look it up in the docs, as this is fundamental knowledge in PW.

Without testing anything in this regard, in my understanding, when config.php is called is to early. Never thought this could / should work. In init.php or ready.php I assume it will work.

Yes it does. For example I often use the Textareas ProField to collect a lot of small textpieces in separate inputfields, but it creates only a single table in DB. On the screenshot you see two db fields / tables, contact and map:

Not sure about the blogging modules, as I don‘t know them. For me this looks like a good fit for urlsegments. Look up the API docs for it, I‘m on mobile. Using this, each of your docs template additionally need a date field, if the user should be able to specify the version date manually. If it should be assigned in an automated way, you can use the page creation_date, (or modified one).

Looks really good! Many thanks! Can‘t wait to arrive into my office and setup my list and add all to my starter profile. Really great! ?

@Robin S really really nice would be, if we can load a custom list with names AND optionally individual download URLs, so that we also can include modules that are not in the official directory. Priority: If a module is selected that has a individual download URL, paste it into the "Add Module From URL" field. What do you think?

Hey @kixe, one question before trying this out: Is it possible to see image thumbnails to select from? I have a use case where I need centralized stored icons and a select field for reference, that shows image thumbnails. Can I do that with your module?

You can post an issue on github, as Ryan may not see this here in the post. But he will see it on Github!

I don't get any letters, but I had deleted my FF-Sync Account because I got doomed by their expired Cert for AddOns. First it deleted my local AddOns and then "uploaded" it to my Sync-Account, what in fact deleted all AddOns there too. For me it was the drop that broke the camel's back. I switched to Opera and there are now only two points of 20+ left which I haven't solved to my satisfaction in Opera yet. In some regards Opera even is a better tool then FF. I really liked it after two weeks using. It seems that this has caused, among other things, a great loss of trust or resentment, which may have led to reduced user numbers. I still use the FF to test websites in the FF, but for nothing else.

This is not an easy question, and so also isn't the answer. Personally I would prefer Git submodules as it would be less effort for users who doesn't have either Git nor Composer understanding. Also Git is very tiny action to install and running, composer seems to take more effort. So, for users who have both capabilities, I also would go with option 3, the composer dependencies. My conclusion is, it depends on your main target group.

@Robin S Many thanks for this. I will try it soon!

@huseyin Welcome to ProcessWire and many thanks for sharing this project with us. Its impressive and well done. ? Paylaştığın için teşekkür ederim

Why do you not include type hidden fields into your forms where you add identifiers? $validFormIdentifier = ['aaaaaaaa', 'bbbbbbb', 'ccccccc']; $myIdentifiedForm = $sanitizer->text($input->post->hiddenidentifier); if(!in_array($myIdentifiedForm, $validFormIdentifier)) { // invalid formsubmission, do not process further }