Jump to content

BitPoet

Members
  • Posts

    1,146
  • Joined

  • Last visited

  • Days Won

    49

Everything posted by BitPoet

  1. I finally found , the new master release 0.0.10 works here with the latest FormBuilder release. Let me know if you encounter any issues.
  2. Hi Ivan, sorry, there's currently no new version. I haven't had the chance to update to a newer FormBuilder release yet, that's on my schedule for December. That will also be the time to give FB Multiplier a bit of an overhaul.
  3. Actually, it does (at least everything but fatal errors). That's one of the reasons (besides information disclosure) you shouldn't use debug mode on a production site.
  4. Glad you're making progress. If only the homepage works, it's usually an issue with RewriteEngine support or RewriteBase not being set correctly in .htaccess (or a missing .htaccess). Make sure you didn't miss any files starting with a "." in the upload.
  5. Since InputfieldTinyMCE appears to make huge steps towards becoming a stable replacement for CKEditor and TinyMCE comes with a native autocomplete API, I just had to try my hands at migrating the autocomplete module I had built for InputfieldCKEditor. Lo and behold, it went even easier than I had hoped. So here - mind you, still very alpha - is my autocomplete module for the new TinyMCE input field. Since I may still introduce breaking changes while things become stable, it will only be available at GitHub for now. Autocompleter for InputfieldTinyMCE What does it do? Autocompleters work like the mention plugin in this forum. You type a "trigger" character (or characters) followed by some letters, and a list of possible results pops up, from which you can choose. InlineCompleteTinyMCE comes with three different autocompleters (called "actions" in the context of this module): Pages: you can configure a selector, just like when you search for pages in the ProcessWire backend. You can search for title, name or any field you would like. Like every action, it allows you to specify templates for the label and the HTML/text to insert. Users: this is the equivalent to the form mention. Type an "@" sign followed by the start of a user name, and it inserts a link to that user. If you have added an image field to the user template, you can display that in the selection popup too. Hanna Code: just type the opening tag ("[[" by default) for your Hanna code and any letter, and the module will look for all codes starting with those letters. You can easily implement your own action modules too. Just inherit from InlineCompleteTinyMCEAction and add the code for a few methods. Enabling Actions For every installed action, you will find a checkbox on the "Input" tab when you configure a field. Configuration for Actions Once you have enabled the action, more configuration options become visible. The exact options depend on the action itself, but you usually have a label template and a value template. You can use placeholders in both. Actions in Action This is what it looks like when used: Compatiblity The module has been tested with InputfieldTinyMCE v6.0.6 both in standalone and inline mode. Lazy loading the standalone editor is also supported. Outlook There's still a bit work waiting for me, from cleaning up some code, over making the Pages action support multiple autocompleters with different triggers and selectors, to adding a lot of documentation. Nevertheless, I'd be happy to get some feedback.
  6. A few more things come mind: check if really all files have been uploaded, as we have seen strange errors with incomplete uploads before. Make sure that uploading to OVH didn't mess with character encodings, and verify that the configured PHP version is actually active (e.g. by placing a small script containing just <?php phpinfo(); ?> in the web root.
  7. I've only ever seen that error message in the context of IMAP, not SMTP. Are you sure your WireMailSMTP configuration is correct? Or are you accessing some IMAP mailbox earlier in the code?
  8. This reads like a namespace issue, which FileCompiler should take care of. Make sure that site/assets (and of course also the directories and files below) is writable by the server. Best clear out the directories in site/assets/cache, then any permission issues should become obvious quickly.
  9. I'm really happy with InputfieldTinyMCE so far. And as threatened to in reply to an earlier core updates post, I took a stab at migrating my autocomplete module over from InputfieldCKEditor. All in all, it was quite a pleasant experience and the JS side was really straight forward. The change also involved a lot of refactoring, and in the aftermath of that there's still a good bit of house cleaning to do, but for anybody willing to toy around with it, there's an alpha release of InlineCompleteTinyMCE on GitHub. A snapshot of InlineCompleteTinyMCEActionUsers in action: And the corresponding configuration in the field's "Input" tab (added to the TinyMCE config section): I haven't tested it with lazy loading or the inline editor yet.
  10. You could call $modules->getModuleInfo('all', ['minify' => false]) and iterate over the results. Each entry has a "core" property and an "installed" property you can check.
  11. Have you tried changing FollowSymlinks to SymLinksifOwnerMatch in .htaccess (it's explained in the comments in section 1. Apache Options)? You should probably even be fine with just commenting out the line in a standard PW setup, so I'd try that first.
  12. That's great. Can't wait to find a bit of spare time to take it on a test drive. Cool that the module is already on TinyMCE 6.2, as that release comes with a more flexible autocomplete api. This is going to shave a lot of (or almost all of the) JS code from my autocomplete module.
  13. Have you looked at $field inside the field template file?
  14. That's what the regular PageReference field (FieldtypePage) is for. Add a new Page Reference field to your template On the Details tab, select "Multiple pages (PageArray)" as the value type On the Input tab, select an Inputfield that supports multiple pages (e.g. AsmSelect) If the dropdown shouldn't show all pages in the site, add limitations in the "Selectable pages" section
  15. It should work if you define the upgrade method as hookable (___upgrade).
  16. A bit of a stab in the dark, but maybe an IPV6 issue? I can see that the test2 host has an IPV6 address while the other does not.
  17. Might be from an unsuccessful curl request (stuff like incompatible cipher suites, untrusted certificate etc.). Have you checked $http->getError()?
  18. Sounds like an incomplete upload (with FieldtypeFile.module being an older version that lacks those method implementations, otherwise FieldtypeImage would inherit them).
  19. Hi @Ivan Gretsky, I will at one point for sure, but that will be late in the year. I‘m currently hiking across the U.S. and won‘t get my hands on a computer until October.
  20. You'd need to turn Event and EventArray into modules programmatically, i.e. add "implements Module" to the class declaration and add the static getModuleInfo() method. The returned array from that method is where you can set the autoload value. Then you can also drop the require_once() statements in the fieldtype's constructor. (And don't forget to install Event and EventArray Modules in the backend after the change)
  21. I'm not sure I'd go down that road, even though it's probably possible. For one, you can't take advantage of the logic already there for numeric field types. For two, what if there are additional price scales? To round it up, for three, it may speed up input, but there will likely be cases where you'll have to disassemble the unformatted value anyway to present the information. I'd go with a repeater that has fields for quantity and price (maybe a default price field on the item page and just add scale prices in the repeater). That way, your data is queryable through selectors, your code will be easier to understand years later when you have to come back and make changes, and you don't have to worry about multiple scales for one item. Price calculation will be just a small piece of code: $price = $item->price; foreach($item->scaleprices->sort('-quantity') as $scale) { if($order->quantity >= $scale->quantity) { $price = $scale->price; break; } }
  22. Have you tried calling $modules->get('yourfieldtype') before using the API? To avoid that, you could turn Event and EventArray into autoload modules.
  23. The wrong is on the side of the module. Too much has changed in the standard datetime field, and I didn't have the time to catch up with these changes. You'll probably have to remove the field and module by hand on the database level (there could be easier ways, but the exact approach probably depends on the exact PHP and PW versions). drop the table field_[yourfieldname] execute the query "DELETE FROM fields WHERE type = 'FieldtypeDatetimeAdvanced';" execute the query "DELETE FROM modules WHERE type = 'FieldtypeDatetimeAdvanced';" delete the module directory Sorry for the hassle. I have added a notice to the module's readme. Unfortunately, I won't find the time to adapt the module before the end of the year.
×
×
  • Create New...