Jump to content

Macrura

PW-Moderators
  • Posts

    2,711
  • Joined

  • Last visited

  • Days Won

    38

Posts posted by Macrura

  1. Hi @fruid - sorry to hear about this! Could you send me the PHP file to have a look at it? Also let me know your PW, PHP and MySQL versions and i'll take a look. You never know, something could have changed with the PW version or PHP 8, and we need to make sure this module keeps working!

    - Marc

    • Like 1
  2. @taotoo thanks for this - and i actually can't recall how that got fixed but i did sync the repo and the fix was probably in there.. I will definitely get around to do a deep dive check and make sure it works and add the AdminThemeCanvas to the code as you have indicated; I didn't even know about that new theme...

    • Like 2
  3. I have no idea if it will work – module config fields can't use a database table, they have to be able to store in JSON, so it would take some research and experimentation to see if it is even possible to use this field type in a module config. So setting schemaClass would have no effect.

    Most module configs that use repeatable interfaces are done with custom javascript, as far as I have seen. (For example use a text field for the first one, and then a hidden field to store the repeatable values; use JS to allow the users to add an inputfield, and then join all of the values together in pipe delimited hidden field..)

    • Like 1
  4. On 7/15/2022 at 10:04 AM, Clarity said:

    Thank you about the information! Can you please tell whether it is possible to use ProField: Multiplier for this module? I'm getting an error "ProcessSettingsFactory: Fieldtype is not set".

    when you do the code to add it, you would need to specify the Fieldtype to multiply, so that needs to be one of the options,

    'fieldtypeClass': 'FieldtypeText' in the json or wherever...

    (haven't tested this, but looking at the module, it does need the "fieldtype to multiply" to be expressly set)

    • Like 1
  5. @Clarity - Settings Factory should technically support what any module config would; i've never seen repeater fields used in a module config screen, probably because repeaters require the use of hidden pages. So for now this module would need to stay limited to those fields whose values can be stored in text/json;

    • Thanks 1
  6. 53 minutes ago, Clarity said:
    Thank you! Finally, I found the root of the problem. I didn't add "return $inputfields;" to the end of file.
    I'm not using a namespace explicitly. ProcessWire version is 3.0.199 dev, and everything works fine now.

    awesome! Thanks for using the module - hope it helps and is useful!

    • Like 2
  7. @Clarity

    Can you post the contents of your PHP file?
    Are you using any namespace?
    What version of ProcessWire are you on?

    There is an example settings file in the module, you can copy to your templates folder somewhere and then specify that file for the settings. If that file doesn't work, then something must have changed in the core. It works for me under PW 3.0.178.

  8. (1) if you are using the textformatter, then you do not need to module init in _init.php

    (2) There is no CSS being output on your page, so the players will not look right

    (3) If everything is automatic, then it should just work, and you shouldn't have to do any code in the header or footer. If you want to use the $config option, then you need to put the foreach for the $config->styles and $config-scripts in the header and footer respectively.

    (4) What does your shortcode look like in the CK editor?

    (5) If you are using Tracy Debugger then you can check the contents of the variables to see what is going on and trace the issue.

    You may also want to look into using Plyr instead of soundmanager;

    Here's an example of how I'm using it instead of SM2, within a CK editor field:

    https://www.equinoxmusic.com/technology/

    https://plyr.io/

     

  9. @Atlasfreeman

    yes technically if it is in the _init, then it should work, unless that variable is out of scope for any reason on this particular file.

    all of the code you showed should all work, so you just need to figure out why those are not working; Did you try the auto option for the assets? How are you getting the JS files to output?

    if the audio is inside a CK editor field then you need to make sure the textformatter is applied to that field in the field settings.

    If you are outputting manually then i think you need to pass the options to the $sm2 instance like is shown in a lot of the posts above with the examples for how to output audio player using the API, as opposed to audio players that live inside a CK editor field and are being parsed like shortcodes, with the textformatter.

     

  10. @Atlasfreeman

    3 hours ago, Atlasfreeman said:

    Or can any of you see another problem?

    >called "textformatterSoundmanager-master" can this be the problem?

    yes, rename it "TextformatterSoundmanager"

    Also you have to output the CSS files - you can choose your output option in the module, but it won't look right without the CSS. So you can output the $config->styles, or use one of the options..

    Let me know how it goes..

    • Confused 1
  11. I think the issue here is that Tracy is running 2x, and thus the JS error;

    For me this usually happens if i am doing an ajax call to an endpoint and that endpoint is still allowing Tracy to run; I couldn't stop tracy with an exit() like i was able to do in the past for some reason, so i had to disable the template in the module settings.

  12. Thanks - yeah I'm thinking about what is best to use - this is a paywall type of situation, and I like that aMember pro has been around for a long time, and is a 1-time payment not an ongoing subscription... I think i will need to use PW users because this client wants a lot of stuff to change for subscribers, like no google ads, etc..

    • Like 1
  13. Awesome write up and thanks so much for this post and the details – very inspiring. I also recently started using HTMX for a lot of things on PW sites, and am similarly impressed and loving it.

    <off-topic> have a site that I need to develop a subscription/membership system for. I'm looking at amember, memberful, and a special setup using Foxycart. All have their pros and cons, but I see that this site uses amember. I wonder if you have any insights about working with amember... </off-topic>

     

     

  14. Hey - cool suggestion; Since Selectize.js is part of the core, this seems like a job for a new module (or hook) – the module/hook would basically initiate the selectize.js assets to be added to the page, as well as a custom js file that would initialize selectize on that field. If I have some time I'll take a look at it..

    • Like 1
  15. i added it, but Github seems to be having a bad day; I also noticed a whole bunch of other new stuff that wasn't committed in the repo, mostly stuff that is attributed to you; I pushed the latest up to GH, and hopefully it will work the same; I haven't had a chance to test it yet today, but will do so soon...

  16. On 9/5/2021 at 8:45 PM, jadon said:

    Will Mailgun's upcoming change to remove plain text smtp passwords from the GET /domains /domains/ endpoints affect this module at all? I have inherited a system that relies on this module so I'm not super familiar with it.

    Thanks.

    Sorry for the delayed response; I'm not sure about this – I will have to look into it, but too much work atm; I should have time in October - hopefully it won't be too late!

    • Like 1
  17. There are just a lot of possible reasons, so hard to say what's happening; You need to check logs, see what the actual errors are, which files errors are in.. explain your complete plan/process as to how you are going to upgrade this. 

    You don't even really need to download and upgrade it; I've done dozens of upgrades on live sites. I'd be more concerned about the PHP version upgrade than the PW upgrade; I've had close to zero issues with PW core upgrades; Issues if any usually come from modules or front end code. Before i upgrade any PHP version that a site is running on, i first upgrade everything to ensure compatibility and then do incremental upgrades if the server offers multiple PHP versions - 7.2, then 7.3; 7.4 seems to have the most breaking changes and i'm currently upgrading many sites and finding 7.4 to be the hardest upgrade.

  18. Here are some quick items to consider, based on how I would upgrade a site:

    - start over, back to the original version (2.5)
    - Login as superadmin
    - enable debug mode from the config
    - Make sure the site is fully functional on localhost in the original version;
        if there are PHP errors/warnings on the front end, e.g. related to php version, fix those first before upgrading the site
    - Upgrade any modules that are compatible with 2.5
    - once the site is running with no errors on 2.5, upgrade the core to latest stable version  
        if you replace the htaccess, make note of any settings that need to be copied over (www, https, pro cache etc)
    - upgrade all modules to the latest using the upgrades module

    Note that the new core compiles the non-namespaced files. You can clear the filecompiler cache (bottom of modules) if you see any errors related to that,

    if you still see no content on the homepage, check for js/browser errors;
    Check how assets are being referenced; paths could not be resolving.

    • Like 1
×
×
  • Create New...