We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 3749
    • 24,544 Posts
    If you have the current version of Articles (I see this in Articles 1.6.1; you may have to upgrade MODX to get a newer version of Articles) you should be able to change the URL format.


    • Right-click on the Articles container and select "Manage Articles"
    • Click on the "Advanced settings" tab at the top
    • Click on the "General" tab on the left
    • Scroll down to the bottom.

    You should see the "Articles URL Format" field.
    The default value is %Y/%m/%d/%alias/


    ------------------------------------------------------------------------------------------
    PLEASE, PLEASE specify the version of MODX you are using.
    MODX info for everyone: http://bobsguides.com/modx.html
      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
      • 39932
      • 483 Posts
      You should see the "Articles URL Format" field.

      This doesn't fix Tags, Quip or Author links... you still have to copy/adjust the Chunks manually or write custom Snippets (which are not in the Elements, but in the Media Source instead). And given that some browsers ignore/implement base_url incorrectly, Articles should follow the link_tag_scheme in the System Settings, but it ignores it.

      That said, Articles is a great add-on, but it is broken for Revo 2.2.4 on a new install. I understand kyrhlik's confusion (and possible frustration) as I had to perform the fixes manually that used to work on a new install in Revo 2.1. When a single important Add-on misbehaves as compared to the entire rest of the system, it can get difficult to make important decisions like choosing an FURL format. sad
        Website: Extended Dialog Development Blog: on Extended Dialog
        Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
        Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

        Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".
        • 39932
        • 483 Posts
        @kyhrlik:

        I have been helping someone make the fixes manually to the Articles, Tags, Authors and Comments. You can first check this post, which starts the process:

        Articles sub-links were working after this one:
        https://forums.modx.com/thread/78718/help-needed-with-articles

        The rest is being done here:
        https://forums.modx.com/thread/78734/articles-comments-not-appearing-on-front-or-back-end-solved


        Notes: The issue is not with MODx, in my experience. It is amazingly well put together, as are most of the add-ons. Articles (one of the most prolific add-ons) just doesn't seem to be working out of the box and there is no documentation about how to fix it. Once it is working, it is an amazing Add-on, though. [ed. note: fuzzicallogic last edited this post 14 years, 2 months ago.]
          Website: Extended Dialog Development Blog: on Extended Dialog
          Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
          Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

          Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".
          • 3749
          • 24,544 Posts
          Could you report that here so it doesn't fall through the cracks?

          http://tracker.modx.com/projects/articles


          ------------------------------------------------------------------------------------------
          PLEASE, PLEASE specify the version of MODX you are using.
          MODX info for everyone: http://bobsguides.com/modx.html
            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
            • 39932
            • 483 Posts
            @BobRay:

            Yuppers. The only reason I didn't before is because I thought I had screwed mine up. It wasn't until the last 4 days reading all of the posts on Articles that had the same issues mine did that I realized it wasn't me.

            I've also been trying to figure out whether it is link_tag_scheme that is broken or makeUrl() and whether or not Articles utilizes makeUrl() or not. I've had ambiguous results with both. That said, [ [ ~ id ] ] works correctly everytime, but I assumed it was using makeUrl(). I didn't want to report the wrong error to the wrong folks. [ed. note: fuzzicallogic last edited this post 14 years, 2 months ago.]
              Website: Extended Dialog Development Blog: on Extended Dialog
              Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
              Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

              Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".
              • 22303 MODX Staff
              • 10,725 Posts
              Quote from: fuzzicallogic at Aug 20, 2012, 05:23 AM
              I've also been trying to figure out whether it is link_tag_scheme that is broken or makeUrl() and whether or not Articles utilizes makeUrl() or not. I've had ambiguous results with both. That said, [ [ ~ id ] ] works correctly everytime, but I assumed it was using makeUrl(). I didn't want to report the wrong error to the wrong folks.
              Is this an Articles issue with it just ignoring the default link_tag_scheme? I cannot find a bug with makeUrl(), which uses the link_tag_scheme setting.

              FWIW, the default behavior is for makeUrl() to render links as relative to the base_url setting, except when rendering links from Contexts other than the current one, in which case the links are made full (since Contexts generally represent other domains or subdomains) automatically by makeUrl().
                • 39932
                • 483 Posts
                I've had problems with makeUrl() using the link_tag_scheme, and I've also had problems with using specific params. On my machine, makeUrl() makes all links relative, rather than absolute (which is my link_tag_scheme). Even if I use makeUrl() with 'abs' as the scheme it doesn't work correctly. The solution for me was to always use [ [~id] ] or to make my own adjustments to the URLs. [ [~id] ] works correctly every time. I've fixed this myself, but in Articles it is a really prevalent issue.

                Articles seems to ignore System Settings entirely, and because it doesn't seem to use [ [~id] ] almost anywhere, much of the linkage is broken out of the box without some major adjustment. Since I use abs as my link_tag_scheme, one would think that it would use that.

                Hopefully, this demonstrates my confusion as to where the problem is and why it hasn't been reported. In fact, for some time, I was convinced it was my own error. I simply don't know "who" the culprit is. In the meantime, if you do a search for Articles in the forums, in the last couple of months, the number of posts exhibiting this behavior has grown dramatically.

                The problem becomes even worse if I use the base element. Articles works correctly, but none of the rest of the site does. This is because MODx correctly makes the link according to the resource hierarchy, and therefore, with 'abs' it prepends with the '/'. In sme browsers this applies an extra slash. Articles, however, depends upon the base element and simply makes the link relative no matter what and this is "appended" by the browser to the base element with no extra slash.

                Those are the details. This conflict in behavior is the cause of the confusion regarding where the issue really lies. As a result, I think most people (like myself) who have to fix it manually think they have done something wrong (like myself). Unfortunately, until I get consistent behavior, I am reluctant to say this is an "issue" with MODx at all. But I also cannot pin it to Articles. More likely, I think it is a combination of a number of factors...

                1) Different browser implement base differently with links that have a prepended slash. 2) Articles makes its URLs relative to the container and love the base element. 3) makeUrl() properly works as expected for most circumstances, but given specific circumstances does not allow the override as a param. 4) My incorrect use of arguments within makeUrl(). [ed. note: fuzzicallogic last edited this post 14 years, 2 months ago.]
                  Website: Extended Dialog Development Blog: on Extended Dialog
                  Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
                  Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

                  Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".
                  • 22303 MODX Staff
                  • 10,725 Posts
                  By default, makeUrl uses -1 as the scheme, which generates URIs relative to the MODX_BASE_URL. 'abs' changes this to make them absolute URIs, which prepend the MODX_BASE_URL. 'full' generates complete URLs, including scheme and http_host.

                  PLEASE NOTE that links generated for a different Context than the current Resource is in will always be 'full'.
                    • 39932
                    • 483 Posts
                    @Opengeek:

                    Understand that I know this.
                      Website: Extended Dialog Development Blog: on Extended Dialog
                      Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
                      Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

                      Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".
                      • 28042 ☆ A M B ☆
                      • 24,524 Posts
                      This might make things a little awkward when using some of your tricks involving contexts. I think it would be better if one could set a context to use the scheme of one's choice, perhaps in the system settings.
                        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