Macrura

You can sell them here: https://processwireshop.pw/

@kixe can you upgrade to 3.0.23. A lot of modules and other stuff was broken on .22

right - the use case is that we have a media library and that holds images that are used in various places on the site. On any of those images in the library, the users should be allowed to use the image marker functionality, or not use it...

working well, like the Lato font; noticing that the top breadcrumb is breaking to 2 lines

I was thinking of using this, but was wondering about the possibility of making it optional, for example in a template where you might want to make it optional to create image markers, is there anyway for the module to not show an error if there is no image in the specified image field. If that's not really possible then we can come up with a work around (using an alternate template etc..) Thanks!

1.) "<article> <h2>{$page->title}</h2> <header class='news-meta'><strong>Date : </strong>{$page->publish_date}</header> <div class='news-content-text'> <p>{$page->summary}</p> </div> <div class='article'>{$page->body}</div> <p><img src='{$image->url}' alt='{$image->description}'></p> </article>"; _main.php should be the global layout; the templates just populate the content variable which is within the content area of the '_main' layout. $page->body is the "body" field (the one with the Rich Text Editor) Closing brackets are not needed and should always be left out when the file ends with php code: https://processwire.com/api/coding-style-guide/#2-general

you could do a hook that rewrites the URL for those child pages to the parent.. doing it 'all the time' in site/ready.php /** * This hook modifies the default behavior of the Page::path function (and thereby Page::url) * this will rewrite the path to children that should not have their own page * any automatic links to the page, e.g. in the admin, will direct to the parent page. * */ wire()->addHookBefore('Page::path', function($event) { $page = $event->object; if($page->template == 'sometemplate') { $event->replace = true; $event->return = $page->parent->path; } });

Latest version of InputfieldSelectize(1.0.1) has some cleanup and multiple version adds support for max items.

So after some hours of testing/research/code experiments, that yielded the modifications I made to the module as noted on GitHub, i can now send messages with the ability to switch between the sending domain and it all works. (also see edited post above). Goodbye Mandrill!

Also the new code button doesn't allow line numbers (?)

cool that you found the selectize inputfield.. hope it works well and let me know if you run into any issues or requests. In combination with the custom PHP option it opens up to almost anything.. hope to be releasing an ajax version sometime in future..

you mean so around line 132 changing like this: switch ($info['http_code']) { case 200: //return true; // Can't set int for number sent, since Mailgun doesn't return that data return 1; // this instead ? break; ...

I'm working on converting a site from WireMailSMTP + Mandrill to using Mailgun. In case anyone else needs to do this i'm posting the steps and snafus here. So far in adapting the existing code, the differences i have logged so far are; 1.) in WireMailSMTP you have to set sendSingle(true) if you want the messages to each be sent individually, but this is the default for WireMailMailgun, so that call gets removed. 2.) the method for adding attachments differs: this: $mail->attachment(string $filepath); becomes this: $mail->addAttachment(string $filepath); 3.) If your site sends from different domains, then you need to switch that setting before send. It appears to me that the API key is the same for all my domains, so I should only need to change the one setting when i send the email assuming i have already entered the API key in the WireMailMailgun module settings, then i can extract the domain of sending email address and set the domain to that (and also assuming I have all of those domains configured in Mailgun). $domain = substr(strrchr($identity->email, "@"), 1); $mail->setDomainName($domain); *** This doesn't actually work because the runtime setting is not overriding the domain that is set in the ___send() options. *** I made modifications to the module and now i have this working with my system; would probably need another setting like "match "sending domain" to "from email" domain" or something and also make the domain field optional in the module settings.. https://github.com/plauclair/WireMailMailgun/issues/7 ------------------------------------------------------------------------------------------------------------ Additional comments and observations: - would also be nice if an attachment() method could simply be added which aliases the other method (would save some code checks)

it wouldn't work with Selectize.js because the fields select there is a special ASM select with nestable ability for the fieldsets. I think the only way would be enable the field itself to have an option of autocomplete. The ideal way would be not to have automcomplete, but instead to have a search filter, because i think most of the time you do want to see all the options, but still be able to find what you want by typing.

ok thanks!

One issue I ran into today was a clash of Ace editors (using latest Tracy) i have ace editors on my InputfieldSelectize module, as well as any field that uses that AceExtended inputfield; seems that i need to disable the tracy console panel to prevent it from affecting the Ace instance. These 2 files are not loading: /site/modules/TracyDebugger/ace-editor/theme-monokai.js /site/modules/TracyDebugger/ace-editor/worker-javascript.js And getting this error: NetworkError: Failed to load worker script at "/site/modules/TracyDebugger/ace-editor/worker-javascript.js"

Cool - thanks! i seem to be clueless on how to do this default data but will check out some other modules and see if i can hack it... in terms of the InputfieldSelectize i think it will be good though to provide the base code to select pages using their title only so then as you say the inputfield will at least be usable out of the box.

@psy thanks for this - nicely done, and looking forward to using this. You should probably remove the closing PHP tags, per the style guide: https://processwire.com/api/coding-style-guide/

Hi Ryan, yes(!), just tested and that appears to be the culprit. I guess i should at least set those default values in the module as you mention, as i'd like to "the right way"

i think the ace is an awesome addition, and can't see why anyone would want plain text.. i'm ok with having the ace in for Tracy, as it could be tricky to handle if someone doesn't have it, and since you only need PHP that makes the requirements less. Adding a config to deal with the big Ace could make things overly complex. Snippets manager would be great!

Just a heads up that the newest version (ProcessWire 3.0.22 devns) breaks some things, one of which is module settings fields on some modules, this being one of them (the Placeholder Text field will not save any value). (Still looking into the cause and hope to discover fix soon as it also affects my inputfield modules). **This is now fixed in 3.0.23 devns**

Thanks as always for this! One problem though that I encountered was that the new version (.22) broke my custom inputfield (InputfieldSelectize), the inputfield seemed to no longer save or load the strings that define the array and option/items markup and then that caused all pages using that to break. is there something that would prevent either storing or loading data into those settings fields (??) Update: The module config data (for each field) is saved to the database, but is not being loaded into the field editor fields when the page renders. This happens on the following modules tested so far: Inputfield Chosen Select Inputfield Selectize Selectize Template & Field Tags if anyone has any clues how to fix this, would be appreciated! I spent some time to look at this but sort of striking out at this stage...

great - thanks for the report; what i like about php.js (which i guess is now Locutus) was being able to grab a function when/where needed from there and pop it right into a project's main.js file and thanks for those references to Lodash and lazy.js, just took a look over at those sites...

cool thanks - yeah this has become indispensable on around 4 big sites at the moment

The module should show up in the directory in a few days. In the meantime, some small fixes and optimizations were made, such as fixed height editor window, and testing on both admin themes. At this time, the fullscreen, side-by-side editing only seems to work on the default theme; in Reno the editor goes behind the left menubar. If anyone has a quick CSS fix for this feel free to post, else i'll have a look at some point when i need to use that mode on reno