Jump to content

Macrura

PW-Moderators
  • Posts

    2,684
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by Macrura

  1. Maybe take a look here: https://github.com/processwire/processwire-issues/issues/1041 https://github.com/processwire/processwire-issues/issues/943 You may need to either install a lower version of PHP, or upgrade to the dev branch latest.
  2. @gebeer Thanks for your work on this! I was going to propose that the module installs a page for use with images, but you have found a possibly better solution with the virtual page. And in terms of this new Fieldtype module using json, and the fact that it supports the SettingsFactory is great, and I hope it didn't cause any issues, but thanks again for going to the nth degree and making this work! Lastly, I only worry about the JsonNativeField in that it requires InnoDB.. guess it might be time to make the switch on sites using MyISAM..
  3. cool! Image picking has been an issue with SettingsFactory... so this will be great 😀. I'll check it out and do some testing asap!
  4. I have this problem on at least 2 sites, and i knew it was the security rules doing it. We're migrating these off to VPS so hopefully it won't be an issue; In the meantime we just don't use the custom field format for the display of the selected pages, and that fixes the issue because it doesn't use those params.
  5. Not true, this it totally legit: $settings = $pages->get("template=settings"); When the setting template is set to only allow 1 page of that type, it will return the settings page; Similarly for the search page, you can do $search = $pages->get("template=search"); this can be safer than referencing by ID – in most cases the search page is 1000, BUT if a client mistakenly trashes the search page, and you create a new replacement search page, then the template selector ends up being safer.
  6. So for the existing version, I was supposed to be copying over your new module into my repo – should I still be doing this with your current version?
  7. not sure if this was reported already, but i'm unable to upgrade past 1.5.54, upgrading from 1.5.54 => 1.5.57 creates a "Failed to init module" error, SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'last_hit'. Hope this helps, not sure what the issue is.
  8. on version 1.2.0 for some reason my javascript files that are compiled with procache have the path to the js file in the beginning of the compiled file which is breaking all js on the site... This isn't happening with the earlier versions of the module.... /home/user/public_html/site/modules/CronjobDatabaseBackup/CronjobDatabaseBackup.js?v=120-1572797219;
  9. https://modules.processwire.com/modules/jquery-ion-range-slider/ this one also works for more complex range needs
  10. @teppo the modified version by @nbcommunication is supposed to replace the current version, but I was trying to find time to test it before replacing the code so as to not potentially have users upgrade and then have broken installations. I just came across a problem with the current version, in that one of my business-critical sites suddenly seems to have lost the ability to send attachments using existing 'official' version; so now i need to work on that - time is the only challenge now, but hoping to get to this within a minimum of the next week...
  11. @J_Szwarga are you wanting to implement in frontend or backend? There's no secret or magic for how to set it up, you can look at a demo here for example: https://fullcalendar.io/docs/initialize-globals-demo and when you see the initialization code, you just need to take a look at the events array, which you could generate in PHP using the API, and then JSON endcode, and output in your script tag.
  12. Ok thanks for the clue, so i have checked the Field List and Values accordion, which I hadn't used before, and i see that the table is corrupted. There is a column outputting a RuntimeMarkup field which contains an admin data table. I have checked the HTML on that and it is all valid; But the existence of that table in the unformatted column of the RuntimeMarkup field's row is breaking the table and causing the next cell to contain the rest of the table inside it. Now looking at the code in the bottom of the source view, i can see that my admin table markup is outputting table tags which are presumably breaking the panel's table markup. I wonder if there is any way to encode that to prevent this... I tried enabling/disabling the $table->setEncodeEntities(true/false) but did not fix the issue. thanks!
  13. I'm having an issue with the Request Info panel randomly not showing various info at the bottom. Here are 2 pages, next to each other – one shows the edit pencil, the other doesn't; this has been happening on several sites.
  14. AFAIK the module does not provide any class to convert array to YAML. the purpose of the module is an inputfield, for YAML formatted text, and has options for output into various formats, but it does not provide any interface for Array to YAML. If you convert your array to JSON, you may be able to find an online converted that can generate YAML from JSON...
  15. @neophron (1) Are you just wanting to output your own player on a page, or use the Textformatter? The Textformatter is for putting in shortcodes into Textarea fields, like Body. (2) The code you posted would only work if you are doing delayed output using a $content var, otherwise if your templates are direct output, you have to echo the content, something like: <?php $options = [ 'type' => 'bar-ui', 'skin' => 'gradient-fat', ]; foreach($page->audio_file as $track) { echo $sm2->player($track, $options); } (3) if you want to use the text field to output an audio player based on a shortcode, then you have to echo the textfield, with the Textformatter applied, like: echo $page->myTextField;
  16. yes, it solves the warning for sure. On a separate topic – is there anyway to set the color of watermark text?
  17. Just a heads up, I'm getting this warning on PHP 7.3.6 : Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home/zzzzzz/dev/site/assets/cache/FileCompiler/site/modules/PageImageManipulator/ImageManipulator02.class.php on line 525
  18. you can just call the module, and format the description, in your template file, at least this is how it works for me: $md = $modules->get("TextformatterMarkdownExtra"); $desc = $image->desc; $md ->format($desc);
  19. you could just store it in a single textarea field and use the AceExtended inputfield. You can just paste that whole block of code into your field, stored in database, and have nice JS syntax highlighting.
  20. getting same thing if using cropping 3rd argument
  21. But what if you (like @Schwab) want a form to not use 3rd party module? If you were coding the contact from then yes, you'd be able to bypass the 3rd party module, but else you have no control over modules that always call the 3rd party WM module; And what if you have a few 3rd party modules installed and want to have control over which one is used and when, not using the API....
  22. @Mikie, thanks for the report, fixed now in next version. In the meantime if you want this fixes, change line 31 in InputfieldSelectize.js from what it is now to this: $(".AdminThemeUikit .InputfieldSelectize select").removeClass('uk-select uk-form-small uk-form-large');
  23. so it seems that modules that send email should always have a way of specifying which WireMail module to use. In other words, Formbuilder should have a setting which scans the installed WireMail modules, and allows the user to select which one to use for FB mails sent; Same for something like ProMailer. The behind-the-scenes selection of which mail module gets used seems to be causing confusion among users, hence the questions on this thread and the issue #733. It also seems possible to have multiple WireMail modules installed which would not conflict with each other, if you always specifically called the module you want to send with, instead of Option A, B or C. I have not tested this theory, but i guess at some point soon there should be some codification of the whole thing...
×
×
  • Create New...