Pending Evolution 1.0 RC2 Release

• • MODX Staff
  • 12,272 Posts
  Ryan Thrash Reply #1, 17 years, 2 months ago

  The main focus of the Evo 1.0 release is fixing a ton of bugs and bringing the Manager and the terms in line where possible with what’s coming in Revo. In addition, Evo should work better for non-English languages and custom Manager themes across the board. You can see the actual roadmap in JIRA (our bug tracker).
  
  Please grab Subversion and start testing important areas prior to the official RC2 release. Some specific areas to review:
  

  
  
  • The Installer is more streamlined and supports RTL languages. Please check your language translation.
  • Likewise, the Manager supports RTL languages from the Manager theme based on MODx Carbon. Evo will require theme updates for existing Add-on Manager themes. Please check your translations here too.
  • The Manager markup and action buttons have been cleaned up. Please check for errors and inconsistencies.
  • Template variable names on internal Manager pages are now referred to by their ID in the database. Plugins that rely on modifying the Manager output (like Manager Manager) need to be updated. The Image Preview plugin distributed with Evo has already been updated.
  • Quick Manager+ has replaced Quick Edit. This will result in loosing the hover boxes and edit buttons on individual content blocks in the front end, but this is a step towards a more robust solution on a maintained code base in subsequent releases.
  • Aliases now support multiple transliteration methods and UTF-8 characters. MODx websites can have multiple transliteration methods in the same site with a TV override. See the new Transalias plugin.
  • A new datepicker based on Mootools replaces the legacy Tigra calendar solution.
  • All internal JS libraries updated to Mootools 1.11 (this will be updated in the future to the most recent release)
  • The Manager login welcome page can now be targeted with a plugin, so custom functionality on your login "dashboard" page can be added.

  
  If you find any bugs, please note the revision number you’re using and open a ticket in JIRA noting it affects the Evo 1.0-RC1 version: http://svn.modxcms.com/jira/secure/CreateIssue!default.jspa Bug reports that include a patch to fix the issue will win you big brownie points.
  
  And finally, feedback and discussion definitely welcome as usual.
  Ryan Thrash, MODX Co-Founder
  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
• • 
  • 1,390 Posts
  kongondo Reply #2, 17 years, 2 months ago

  May I just say that I have tested the SVN version and I am wowed! QM+ is brilliant the the JS effects nice. The action buttons look cool and are just the right size. Btw, the manager is soooo fast, or is it just me? (tested on FF 3.5).
  
  Will PHP 5.3 be supported? I hope so. Thanks.
  
  OK, this is probably not the feedback you want but thought hey, nothing wrong with giving this version some love! Great work!
  
  cheers/k
  Wayfinder Lessons: The (almost) Complete Guide to Creating Menus in MODx Using Wayfinder
• • MODX Staff
  • 12,272 Posts
  Ryan Thrash Reply #3, 17 years, 2 months ago

  PHP 5.3 means the manager/parser needs some TLC. It might not make the 1.0 release, but a point release shortly thereafter is probable. Thanks for the feedback.
  Ryan Thrash, MODX Co-Founder
  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
• • MODX Staff
  • 12,272 Posts
  Ryan Thrash Reply #4, 17 years, 2 months ago

  Current SVN should work with PHP 5.3 now without issue. Tests appreciated!
  Ryan Thrash, MODX Co-Founder
  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
• • 
  • 1,390 Posts
  kongondo Reply #5, 17 years, 2 months ago

  Quote from: rthrash at Jul 23, 2009, 01:25 AM

  
  Current SVN should work with PHP 5.3 now without issue. Tests appreciated!
  

  
  Brilliant!
  
  cheers/k
  Wayfinder Lessons: The (almost) Complete Guide to Creating Menus in MODx Using Wayfinder
• • 
  • 1,390 Posts
  kongondo Reply #6, 17 years, 2 months ago

  OK,
  
  Just updated to rev. 5474 including sample content and all . No errors in the backend but enough parse errors in the front end. Thankfully, the are all mostly similar
  
  I will report this properly later on today (JIRA) but quickly these are mostly to do with the modx_event_log table
  
  MODx Parse errors:
  
  

  1. Execution of a query to the database failed - Incorrect integer value: '' for column 'user' at row 1 »
  SQL: INSERT INTO `evosvn`.`modx_event_log` (eventid,type,createdon,source,description,user) VALUES(0,3,1248345687,'Parser','\n \n \n \n \n
  
  2. Execution of a query to the database failed - Data too long for column 'description' at row 1 »
        SQL: INSERT INTO `evosvn`.`modx_event_log` (eventid,type,createdon,source,description,user) VALUES(0,3,1248345687,'

  
  
  Also get "MySQL server has gone away error"
  
  PHP errors/warnings:
  
  

  1. date(): It is not safe to rely on the system\'s timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function.
  
  2.  Error type/ Nr.:	Warning - 2	 
    File:	..\manager\includes\document.parser.class.inc.php(770) : eval()'d code	 
    Line:	459

  
  
  Environment:
  
  Apache 2.2; PHP 5.3; MySQL 5.1.36; FF 3.5; Iron (chrome clone)
  
  cheers/k
  
  btw: for those who care, noticed these errors rendered faster in Iron compared to FF 3.5 which basically hangs for a while...
  Wayfinder Lessons: The (almost) Complete Guide to Creating Menus in MODx Using Wayfinder
• • MODX Staff
  • 1,535 Posts
  Garry Nutting Reply #7, 17 years, 2 months ago

  @kondongo: The parse errors on the frontend look related to a snippet that is running - any chance you could try and isolate which snippet is causing the problem? It may also be the parse error that is causing the problems with inserting the record into the event log, but not sure at this stage.
  
  The date timezone error is also something I had when I upgraded to PHP 5.3, it seems the stock PHP 5.3 doesn’t set a value for this - to correct the problem, edit your php.ini file and add in a recognized timezone value for the ’date.timezone’ setting. There’s a whole list of accepted timezones at: http://us.php.net/manual/en/timezones.php
  Garry Nutting
  Senior Developer
  MODX, LLC
  
  Email: [email protected]
  Twitter: @garryn
  Web: modx.com
• • 
  • 1,390 Posts
  kongondo Reply #8, 17 years, 2 months ago

  Quote from: garryn at Jul 23, 2009, 07:47 AM

  
  @kondongo: The parse errors on the frontend look related to a snippet that is running - any chance you could try and isolate which snippet is causing the problem? It may also be the parse error that is causing the problems with inserting the record into the event log, but not sure at this stage.
  
  The date timezone error is also something I had when I upgraded to PHP 5.3, it seems the stock PHP 5.3 doesn’t set a value for this - to correct the problem, edit your php.ini file and add in a recognized timezone value for the ’date.timezone’ setting. There’s a whole list of accepted timezones at: http://us.php.net/manual/en/timezones.php
  

  
  Houston we have lift-off!
  
  ListIndexer is culpable...Didn’t check what part of the code specifically though...
  
  MAJOR EDIT: ListIndexer is not to blame per se...it is colluding with the date.timezone setting Once I set my time zone, all was well in the kingdom again; peace has returned and folks are living together happily...everything works, INCLUDING ListIndexer, no more errors..
  
  Thx for the timezones info.
  
  cheers/k
  
  btw: nice addition, the drop down for the save button.. i.e. continue editing, close, etc...
  Wayfinder Lessons: The (almost) Complete Guide to Creating Menus in MODx Using Wayfinder
• • 
  • 1,390 Posts
  kongondo Reply #9, 17 years, 2 months ago

  Uh, oh...spoke to soon
  
  Errors when one clicks on the blog...
  
  I get the same MODx parse errors as noted in my previous post above including a new PHP error:
  
  

  PHP error debug
    Error:	func_get_args(): Called from the global scope - no function context	 
    Error type/ Nr.:	Warning - 2	 
    File:	..\manager\includes\document.parser.class.inc.php(770) : eval()'d code	 
    Line:	274

  
  
  /k
  Wayfinder Lessons: The (almost) Complete Guide to Creating Menus in MODx Using Wayfinder
• • MODX Staff
  • 1,535 Posts
  Garry Nutting Reply #10, 17 years, 2 months ago

  Hi kongondo, yes we’re getting that func_get_args() error as well and currently debugging it as we speak (well, type)!
  
  EDIT: Thanks to netProphET, the above issue has now been fixed in SVN
  Garry Nutting
  Senior Developer
  MODX, LLC
  
  Email: [email protected]
  Twitter: @garryn
  Web: modx.com

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