We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 10487 MODX Staff
    • 1,535 Posts
    Forgive me if this question is basic...what changes can I make for this to validate properly?
    rasc is correct - if the plugin and module are installed, it is most likely that you don’t have the plugin assigned to the ’OnWebPagePrerender’ event.
      Garry Nutting
      Senior Developer
      MODX, LLC

      Email: [email protected]
      Twitter: @garryn
      Web: modx.com
      • 24495
      • 407 Posts
      Yes, that was the second I forgot after first using autolink grin
        • 18973
        • 61 Posts
        Thanks guys. Just got a little impatient there for a minute, but everything turned out great. Autolink is really slick.
          • 17673
          • 194 Posts

          I just discovered Autolink... how come nobody is discussing about it?!
          it is a great tool for accessibility-aware, multi-lingual sites!

          one suggestion for the readme.txt:
          [tt]"The plugin only runs on content that is between the <body></body> tags."[/tt]

          After reading this I first tried to include my whole template between the autolink tags:

          [tt]<body>
          <autolink>
          <div id="wrap">
          <div id="header">
          ...
          </div>

          <div id="column1">
          ...
          </div>

          [...]

          </autolink>
          </body>[/tt]

          but in order to actually get the links etc, I instead had to wrap each content block in the <autolink>...</autolink>; is there a better way?


          One question about the modified version for ’lang’ support:
          how does it work?! I have pasted the modified plugin and module code in the manager but I don’t see an extra lang-checkbox in the keyword editing form, any special sintax to be used in ’value’ or other fields for this to work ?!



          Thanks, ciao


            ----------------------------------------------------------
            http://www.linkedin.com/in/lucapost/
            http://www.twitter.com/lukwe/
            ----------------------------------------------------------
            • 24495
            • 407 Posts
            Hi lukwe,

            there is no checkbox for lang support. you’ll find an answer at http://modxcms.com/Autolink-0.html in instructions:
            language marking: put the keyword and set the value to "enLang"
            . that means: type "enLang" into the value field. that’s all.
            there is only an option for English language, but you can modify the plugin for other languages. Please look into the code.

            happy new year,
            rasc
              • 17673
              • 194 Posts


              * acronym: put the keyword, the value and set the radio button to "acronym"


              Acronym: in my tests I’m actually seeing that nothing from ‘value’ makes its way into the rendered HTML, I’m using just the ’title’ field (?)

              Language: ’enLang’ works and I added an equivalent block to support ’itLang’ for italian, as needed in my installation.

              Accessibility guidelines state that language changes should be tagged with respect to the default language for the document, as set in the HTML tag:

              [tt]<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="it" lang="it">[/tt]

              Autolink should check these fundamental page attributes and act accordingly; otherwise in a multilingual site we would find english docs full of superfluos language-change <span>s to english (for any term defined as a keyword for the other language content) and viceversa!

                ----------------------------------------------------------
                http://www.linkedin.com/in/lucapost/
                http://www.twitter.com/lukwe/
                ----------------------------------------------------------
                • 10487 MODX Staff
                • 1,535 Posts
                Nice idea, lukwe! I’ll definitely look into that for the next version smiley

                @all: There is a new version in the pipeline but it’s coming along quite slow at the moment as I’ve just not had the time recently - but it is slowly, line by line, getting towards a release. wink

                It is going to have a module rewrite, various methods for grouping keywords and setting publish/unpublish dates as well as scheduling when keywords should be linked, a number of accessibility tweaks that people have mentioned, and hopefully a new parsing method that should speed things up.

                Keep the ideas coming and I’ll see about getting them added to the to-do list, thanks everyone!
                  Garry Nutting
                  Senior Developer
                  MODX, LLC

                  Email: [email protected]
                  Twitter: @garryn
                  Web: modx.com
                  • 17673
                  • 194 Posts

                  Glad to hear that you are working on new features, I really believe this is a very important tool, worth a mention along with all the Ajax-hype on the MODx homepage! shocked
                    ----------------------------------------------------------
                    http://www.linkedin.com/in/lucapost/
                    http://www.twitter.com/lukwe/
                    ----------------------------------------------------------
                    • 17673
                    • 194 Posts

                    Ooops I just thought about another possible extension: microformats, hcards etc !?

                    As the scope of the argument is wide, this would be better implemented in its own module/snippet but most of the autolink code could probably be re-used as a start

                    ...maybe we should also discuss this in a new thread!

                      ----------------------------------------------------------
                      http://www.linkedin.com/in/lucapost/
                      http://www.twitter.com/lukwe/
                      ----------------------------------------------------------
                      • 17673
                      • 194 Posts

                      1)
                      <abbr> does not work correctly, it just outputs <abbr>...</abbr> tags, ignoring what I enter in Title -it should generate <abbr title="whatever">...</abbr>

                      I have fixed it by myself in my copy, just making sure this get fixed in next release.

                      2)the xml:lang="en" part of the language is required only in XHTML strict (i.e. does not validate if the document is set to HTML 4.01 strict), hence autolink should check on the Doctype and or have an option to include/exclude this.
                        ----------------------------------------------------------
                        http://www.linkedin.com/in/lucapost/
                        http://www.twitter.com/lukwe/
                        ----------------------------------------------------------