We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 33497
    • 30 Posts
    We’re using ISO 8859-1. Since the 0.9.6 update ModX throws a PHP strstr() error, when I try to save an modified document:
    Warning: strtr() [function.strtr]: The second argument is not an array. in /homepages/33/d105031732/htdocs/manager/processors/save_content.processor.php on line 859
    

    Beside that it throws another error "document X is allready using alias ’’" - but the alias is properly set on the document. Its _not_ empty.

    When I set it empty another error occures together with the strstr() warning:
    Warning: Cannot modify header information - headers already sent by (output started at /homepages/33/d105031732/htdocs/manager/processors/save_content.processor.php:859) in /homepages/33/d105031732/htdocs/manager/processors/save_content.processor.php on line 563
    


    When it throws the modify header warning it still saves the changes on the document.
    But I am just able to save it when I delete the documents alias. After that ModX throws the header warning, saves my changes and sets the alias silently to 1 regardless if another document allrady has that alias or not.
    Whats going wrong here?


    "Solution:"
    Set encoding to UTF-8 (this way everything works as it should) replaced the umlauts with their html entities &*uml; and fixed all broken document alias.
    After that set encoding back to iso.
    This ’solution’ is ok to fix the alias so the menu’s still work.
    But it is impossible to create new documents it wouldn’t be fun to replace all umlauts.
      • 22303 MODX Staff
      • 10,725 Posts
      This was reported and fixed in SVN shortly after 0.9.6 release, and we’ll have the fix in the next maintenance release, 0.9.6.1, likely in a few days time.
        • 33497
        • 30 Posts
        Thanks (for saving me from going mad wink)

        btw:
        Is the a Bugzilla o.s. out there?
          • 33497
          • 30 Posts
          Quote from: OpenGeek at Jul 19, 2007, 08:45 AM

          This was reported and fixed in SVN shortly after 0.9.6 release, and we’ll have the fix in the next maintenance release, 0.9.6.1, likely in a few days time.

          So whats the status of that maintenance release? Seems like the ModX dev’s days are a bit longer than mine rolleyes