On March 26, 2019 we launched new MODX Forums. Please join us at the new MODX Community Forums.
Subscribe: RSS
  • Hi, I am just trying to figure out, the add-ons "SubscribeMe" and "Login". Maybe someone has experience with making paid subscription and with these extras? Does "SubscribeMe" add-on create front-end users or do I need to install "Login" extra and make them work together? Are they both compatible one with another and work together? Or maybe "SubscribeMe" + "mhPayPal" is better solution?
    • AFAIK, SubscribeMe is no longer being developed or supported and it's gone from modx.com/extras. That doesn't mean that it won't work, but it wouldn't be too surprising if it didn't work with the current version of MODX.

      The Subscribe extra (not to be confused with SubscribeMe) is an option, but it doesn't do payments. It might be possible to combine it with a PayPal platform, but I've never tried it.

      Another option would be the Register snippet (part of the Login package) combined with mhPayPal. It will gather information in a form will and run other snippets as "postHooks". I think it might also be possible to have an mhPayPal snippet tag and a Register snippet tag (or a tag for a modified version of the Register snippet) on the same page that processed selected information in the same form.

      Since Subscribe uses the Register snippet, you could also add Register postHooks there too. Subscribe is really helpful if you want to let users manage their preferences (like tags/interests) or user group memberships.

        Did I help you? Buy me a beer
        Get my Book: MODX:The Official Guide
        MODX info for everyone: http://bobsguides.com/modx.html
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting
      • Thanks BobRay.
        • In my case, I need to sell sort of a single product via PayPal and that product is a registration for a certain period of time with expiration date. The most important thing is to make user activation automaticly after the payment is done. I am gonna need to modify DB to have extra fields to keep additional data about the front-end users like expiration date and etc.
          So, which one is better in this case? I saw Bob you are a developer of the Subscribe add-on so probably you know this one better than anyone else.
          It would be great to have one big serious module for ModX instead of few small ones for full registration functionality: free and paid registrations, usual members and subscriptions with and without expiration, optional custom fields for DB to store site specific info about users.
          • If I were doing what you're doing, I think I'd use the ClassExtender extra to extend the modUser Object and add your fields. They would go in a separate table, but still could appear on the Create/Edit User form in the Manager. I would use Subscribe (and Notify if you need to send messages to your users). I think a postHook on the Register snippet could save the user data from the Register form to the extended user fields (and record user preferences if you need them for Subscribe -- e.g., email preferences).

            I'd separate the PayPal process to a separate page with a snippet or processor that would get the information back from PayPal and set the appropriate extended user fields, and forward the user to a welcome page with a link, or links to where they might want to go.

            I'd also put a simple snippet on the protected pages (or in their template) that checked the custom table to see if the user had a current paid subscription, and if not, forwarded them to the PayPal page, perhaps with a $_POST or $_GET variable indicating if they were new (never paid) or needed to renew.

            Another approach (still using Subscribe and the general techniques above) would be to shoehorn your user data into unused fields in the modUser or modUserProfile objects:


            remote_key (string)
            remote_data (json)
            hash_class (string)
            createdon (timestamp)


            mobilephone (string)
            dob (integer)
            gender (integer)
            address (string)
            country (string)
            city (string)
            state (string)
            zip (string)
            fax (string)
            photo (string)
            comment (string)
            website (string)
            extended (json)

            That would avoid extending the modUser object, but would require some messing with the Lexicon strings used for the field captions, and you'd have to remember which field held which data, since the field names wouldn't tell you. You'd also need check the field lengths in the DB to make sure your data would fit.

            Hope this helps. smiley

              Did I help you? Buy me a beer
              Get my Book: MODX:The Official Guide
              MODX info for everyone: http://bobsguides.com/modx.html
              My MODX Extras
              Bob's Guides is now hosted at A2 MODX Hosting
            • Author of SubscribeMe here, just to confirm what Bob said, it is indeed no longer supported and has not been available from MODX.com in years with no plans to bring it back. It's not a viable option to consider, period.
                Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

                Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.