We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 23183
    • 102 Posts
    thanks etal! Will look into the anything rating snippet
      • 19309
      • 49 Posts
      New site, new problem sad

      The TXNewsletters snippet call doesn’t lead to the display of a subscription form but to an error message:



      Parse error: syntax error, unexpected ’:’ in /www/htdocs/w00bec78/pusteblume/manager/includes/document.parser.class.inc.php(770) : eval()’d code on line 97

      Turning Friendly URLs on and of has no effect. I avoided possible interferences with the EMailObfuscate plugin by turning it off for all pages with subscription forms. Interesting enough this staging area installation of a client’s website is more or less equal to the test installation which I used to test TXNewsletters without problems: A standard MODx installation with two extensions: TXNewsletters and EMailObfuscate.

      Anyone had this before and perhaps knows how to fix it?


      Problem solved: I wanted to change a “.” into a “:” on the confirm page. Mistakenly I didn’t change the language file but the snippet. So there really was a “:” in the snippet where a “.” should be. That’s why the error message was displayed.

      In short: Me stupid. undecided
        • 10190
        • 187 Posts
        Hi,

        I’ve tried to get 0.9 running for the first time, but everytime I start the module in the manager I only get a blank page, no button to generate the database tables.

        Any clues?

        Cheers,
        Frisco
          • 25260
          • 156 Posts
          Damn, this module has got a few bugs...

          But since I absolutely need a newsletters module, I think I’ll try to correct them (as my time, knowledge and other works allow).

          Stay tuned smiley
            • 10190
            • 187 Posts
            I think it was about the xml definition file - I uploaded a german one, after removing it, leaving TXNewsletters with the standard ones only the module in the managerin works.

            I then was having problems with the subscription page - a valid email adress "[email protected]" was answered with "please fill in your email adress", a gmx.net adress worked.

            I guess there is a problem with the email validation, only working with domain.tld, but not with sub.domain.tld.

            I now try to get double-opt-in working (I was told TXNewsletters should be able to handle this) - I need TXNewsletter to send a confirmation to the email adress so it can be confirmed that the user really wants the newsletter (German legal issue), and I don’t know how to customize the xml to get the form translated to German and leave some fields out (should I just delete it from the xml)?

            Could someone point me to more documentation then provided with the module itself?

            Cheers
            Frisco
            Frisco
              • 9130
              • 171 Posts
              I then was having problems with the subscription page - a valid email adress "[email protected]" was answered with "please fill in your email adress", a gmx.net adress worked.
              I tested this and you are right this is a bug, the email validated with a big regular expression found in the valid_email function in txnewsletters.inc.php if you want to change it.

              I now try to get double-opt-in working (I was told TXNewsletters should be able to handle this) - I need TXNewsletter to send a confirmation to the email adress so it can be confirmed that the user really wants the newsletter (German legal issue), and I don’t know how to customize the xml to get the form translated to German and leave some fields out (should I just delete it from the xml)?
              The module initialization works in a strange way, you first edit the xml to suit your needs, delete anything you don’t need, and then create the tables in the db. When creating the tables the module reads the xml and builds the tables according to that information. If you already have the tables in the db you will need to drop the txnewsletters_usersdata table, edit the xml and create it again.

              Could someone point me to more documentation then provided with the module itself?
              Sorry, all the documentation we have comes with the module in the README.nfo file.
                • 25260
                • 156 Posts
                May I ask who is working on correcting TXNewsletters bugs, to join forces?
                  • 19889
                  • 616 Posts
                  trying to go into preview or clicking on unsubscribe is resulting in an error - the preview for instance seems to expect /index.php - however my installation is in a sub-dir - do I need to set the correct path somewhere?

                  thanks
                    • 19309
                    • 49 Posts
                    Quote from: mmjaeger at Nov 12, 2009, 09:49 PM

                    however my installation is in a sub-dir - do I need to set the correct path somewhere?

                    Have a look at this post. There I collected all of the fixes I could find in the forums and put it into a (not yet fully tested, but working) version of the module.

                    Nacnud’s solution for using TXNewsletters with a MODx installation placed in a subdirectory is also included. No need to adjust paths in the php files by hand.
                      • 10190
                      • 187 Posts
                      Hi,

                      I use the version of TXNewsletters with support for double-opt-in, and have found some minor problems, maybe someone can help me out?


                      • I need to have a comment inside the xml, saying something like "fields with * are mandatory". How should I do this?
                      • The confirmation email has two same entries in the to-field ([email protected], [email protected]
                      • The encoding of the email seems to be wrong, leading GMX to say "this could be SPAM".
                        Here’s what I find in my headers: Line with the topic can’t handle german umlaute: "*** GMX Spamverdacht *** Bitte bestXXtigen ..." (double X should be an ä)
                        X-Amavis-Alert: BAD HEADER SECTION, Non-encoded 8-bit data (char C3 hex): Subject: ...amverdacht *** Bitte best\303\244tigen Sie die [...]
                        ...
                        Content-Type: text/html; charset=UTF-8
                        Content-Transfer-Encoding: 8bit

                      Any clues how to handle this?

                      Cheers
                      Frisco