We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 16429
    • 254 Posts
    Doze, do you think you can insert a way to use the lightbox one prefers?
    Can be as simple as disabling javascript and css registering if someone use &js and &css, or another param to disable it, but still retaining the rel=lightbox in the links. Basically, every lightbox reacts to the same "rel" attribute.

    Well, I speak for portability because directly modifing it is very simple.
      kudo
      www.kudolink.com - webdesign (surprised?)

      [img]http://www.kudolink.com/kudolinkcom.png[/img] [sup]proudly uses[/sup] [img]http://www.kudolink.com/modx.png[/img]
      • 27889
      • 415 Posts
      Thank you Susan, no way to escape them ?
        MODx Sites & Prestations: http://dp-site.fr [Last MODx Site]
        MODx Repository: [HOME] [MetaTagsExtra] / Current Dev: [xFDM]
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        No, that’s why there are either blocks of code to replace "placeholders" for them, or a snippet is run from a wrapper snippet using $modx->runSnippet(). If you think about it, it has to be that way because the ?, & and = are used in the snippet tags themselves. On the other hand, snippets could be parsed in such a way that anything inside the backticks `` is passed over, but that would be in the core, and I have no idea how that would work.
          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org
          • 7923
          • 4,213 Posts
          Quote from: kudolink at Nov 30, 2006, 12:18 PM

          Doze, do you think you can insert a way to use the lightbox one prefers?
          Can be as simple as disabling javascript and css registering if someone use &js and &css, or another param to disable it, but still retaining the rel=lightbox in the links. Basically, every lightbox reacts to the same "rel" attribute.

          Well, I speak for portability because directly modifing it is very simple.
          Why you need a way to disable it? Why can’t you simply do your own custom template(s) that puts that rel attribute where you want..?


            "He can have a lollipop any time he wants to. That's what it means to be a programmer."
            • 16429
            • 254 Posts
            Quote from: doze at Nov 30, 2006, 03:11 PM

            Quote from: kudolink at Nov 30, 2006, 12:18 PM

            Doze, do you think you can insert a way to use the lightbox one prefers?
            Can be as simple as disabling javascript and css registering if someone use &js and &css, or another param to disable it, but still retaining the rel=lightbox in the links. Basically, every lightbox reacts to the same "rel" attribute.

            Well, I speak for portability because directly modifing it is very simple.
            Why you need a way to disable it? Why can’t you simply do your own custom template(s) that puts that rel attribute where you want..?

            For portability and simplicity, as I said, I think this can resolve the problem directly. But I confess I didn’t look at this possibility so thank you to pointing it out.
              kudo
              www.kudolink.com - webdesign (surprised?)

              [img]http://www.kudolink.com/kudolinkcom.png[/img] [sup]proudly uses[/sup] [img]http://www.kudolink.com/modx.png[/img]
              • 7923
              • 4,213 Posts
              Quote from: kudolink at Nov 30, 2006, 06:57 PM

              For portability and simplicity, as I said, I think this can resolve the problem directly. But I confess I didn’t look at this possibility so thank you to pointing it out.
              Ok.. I’m pretty sure that I wont be doing that option, because it can be achieved very easily by doing your own custom templates.. that’s what they are for. The default templates are just to be used when you are happy enough with the built in features, but if you want to do some modifying, custom templates are what you need to use.


                "He can have a lollipop any time he wants to. That's what it means to be a programmer."
                • 26435
                • 1,193 Posts
                I am getting a strange occurrence when I place a [[MaxiGallery?]] call and a [[Jot?]] call on the same page. it breaks. It takes about 40 seconds to load (like maybe it is trying to parse something) and then finally it returns a blank page. viewing the source of this blank page is completely empty. I wonder if it is something to do with PHx being used in both of the snippets. I have MaxiGallery 0.5 beta 2, Jot 1.0.1, and PHx 2.1.1.

                -sD-
                Dr. Scotty Delicious, Scientist.
                  Husband, Father, Brother, Son, Programmer, Atheist, Nurse, Friend, Lover, Fighter.
                  All of the above... in no specific order.


                  I send pointless little messages
                  • 7923
                  • 4,213 Posts
                  If you use PHx as separate plugin, Maxigallery and Jot won’t be including their own, so that should not be the problem. You also seem to have the latest versions of each, so don’t know what the problem is.. I suspect it’s something to do with PHx though.. Does Maxigallery and Jot work fine if in separate documents? Have you tried to disable the PHx plugin and let Maxigallery and Jot use their own? I don’t know if bS has fixed the class collision in Jot yet, but try.. Anyways, I think that bS would have better input on this issue, I’ll notify him.


                    "He can have a lollipop any time he wants to. That's what it means to be a programmer."
                    • 26435
                    • 1,193 Posts
                    Quote from: doze at Dec 11, 2006, 11:17 AM

                    If you use PHx as separate plugin, Maxigallery and Jot won’t be including their own, so that should not be the problem. You also seem to have the latest versions of each, so don’t know what the problem is.. I suspect it’s something to do with PHx though.. Does Maxigallery and Jot work fine if in separate documents? Have you tried to disable the PHx plugin and let Maxigallery and Jot use their own? I don’t know if bS has fixed the class collision in Jot yet, but try.. Anyways, I think that bS would have better input on this issue, I’ll notify him.
                    Well, I did a few tests. Both Jot and MaxiGallery work splendidly when called on separate documents. With the PHx plugin disabled, results are identical. Thank you for your response doze. I will take some time to look into this issue and I will post a solution as soon as I discover the problem.

                    regards,

                    -sD-
                    Dr. Scotty Delicious, Scientist.
                      Husband, Father, Brother, Son, Programmer, Atheist, Nurse, Friend, Lover, Fighter.
                      All of the above... in no specific order.


                      I send pointless little messages
                      • 16429
                      • 254 Posts
                      Quote from: doze at Dec 01, 2006, 07:40 AM

                      Quote from: kudolink at Nov 30, 2006, 06:57 PM

                      For portability and simplicity, as I said, I think this can resolve the problem directly. But I confess I didn’t look at this possibility so thank you to pointing it out.
                      Ok.. I’m pretty sure that I wont be doing that option, because it can be achieved very easily by doing your own custom templates.. that’s what they are for. The default templates are just to be used when you are happy enough with the built in features, but if you want to do some modifying, custom templates are what you need to use.
                      You’re definitely right.
                        kudo
                        www.kudolink.com - webdesign (surprised?)

                        [img]http://www.kudolink.com/kudolinkcom.png[/img] [sup]proudly uses[/sup] [img]http://www.kudolink.com/modx.png[/img]

                      This discussion is closed to further replies. Keep calm and carry on.