Bringing Evo back to life again

• • 
  • 164 Posts
  soushi Reply #301, 14 years, 4 months ago

  The pilot edition of yama was prepared on Japanease demo site.
  
  [Demo site URL]
  http://mng.demo.modx.jp/en/index.html
  
  In Demo site , you can choose MODX from the lists and can try this MODX freely.
  MODX site is deleted in 24 hours.
  
  

  
  
  • Pilot edition of yama(Enable bypass cache mode)

  
  
  The following is a digression.
  
  

  
  
  • This MODX Evo is using PDO experimentally.

  
  
• • 
  • 222 Posts
  Stefanie Reply #302, 14 years, 4 months ago

  Hi soushi,
  
  Where can I take a look into the sources of the PDO version?
  
  Because I am working on bringing Evo up with ezSQL, I would like to see what was done there.
  Gone away and found a better place to stay
• • ☆ A M B ☆
  • 1,231 Posts
  yama Reply #303, 14 years, 4 months ago

  It is necessary to add one chunk to a live demo site.
  
  http://code.google.com/p/modx-ja/downloads/detail?name=chunk.zip
  Please install this chunk.
  Chunk name is be "custom loginscreen"
  
  
  Plain style (as customizable base)
  
  
  Custom style [ed. note: yama last edited this post 14 years, 4 months ago.]
• • ☆ A M B ☆
  • 1,231 Posts
  yama Reply #304, 14 years, 4 months ago

  My currently next tasks
  
  

  
  
  • Handling million pages(1,000,000pages)
  • Core native handring, PHx format
  • System auto update
  • Use Token method solution (CSRF attack)
  • Resource edit screen customization

  
  And,
  
  http://mng.demo.modx.jp/en/index.html
  Add hundred pages(100) in a container, it's hidden in tree. Please try. Basic weblog is OK.
  And, can use right click context menu in resource list view.
• • 
  • 172 Posts
  TimGS Reply #305, 14 years, 4 months ago

  I have started a new thread at https://forums.modx.com/thread/76367/handling-content-in-multiple-languages#dis-post-422475 to discuss handling content with multiple languages.
  
  -- Tim.
  
• • 
  • 486 Posts
  nickf08 Reply #306, 14 years, 4 months ago

  This progress sounds so exciting.
  
  Thanks to all for doing such an awesome job and for keeping the Evo improvements rolling.
  
  I love your work.
  Web design Adelaide
  http://gocreate.com.au
• • 
  • 164 Posts
  soushi Reply #307, 14 years, 4 months ago

  Hi Stefanie ,
  
  

  Where can I take a look into the sources of the PDO version?
  Because I am working on bringing Evo up with ezSQL, I would like to see what was done there.
  

  
  The PDO version is committed here.
  
  [dev_pdo branch top]
  https://github.com/modxcms-jp/evolution-jp/tree/dev_pdo
  
  [dev_pdo branch history]
  https://github.com/modxcms-jp/evolution-jp/commits/dev_pdo/
  
  The present PDO version has simply imitated existing MODX DBAPI.
  I think that PDO version will correspond to 'PDO::prepare' in the future.
  I think that it is simpler, it is secure,and it is easy when will correspond to another DB in the future.
  
  yama write:
  

  It is necessary to add one chunk to a live demo site.

  
  Demo site was changed into the package containing this chunk.
  
  http://mng.demo.modx.jp/en/index.html
  
  
• • 
  • 222 Posts
  Stefanie Reply #308, 14 years, 4 months ago

  Thank you soushi, for sharing the source, as I'm currently running into a problem running ezSQL, because it returns arrays instead of objects, I would have to rewrite some more code.
  
  There is also a some work to do, because the installer must be changed, that one uses direct MySQL connections, instead of the DBAPI class.
  
  At the beginning of this thread we had a discussion about PDO, or not. I feared, that it might bring some trouble with end users, as that happened to Revo using PDO.
  Gone away and found a better place to stay
• • 
  • 222 Posts
  Stefanie Reply #309, 14 years, 4 months ago

  I just merged the branch 1.1.dev.japanese into the 1.1.dev branch and fixed the conflicts, which was only say yes to a change of the big Japanese commits.
  
  Our current main branch 1.1.dev is working, one can install the sample page and I've found no problems working with an installation.
  
  Therefore, the huge amount of changes by the Japanese community have arrived to a reunion of code
  Gone away and found a better place to stay
• • 
  • 222 Posts
  Stefanie Reply #310, 14 years, 4 months ago

  At the moment I'm going to merge my code cleaning with the the changes by the Japanese community.
  There is a problem, because the order of the functions in the class DocumentParser class is changed. That does mean, that I have to merge the changes manually. This work will take some time.
  
  I really prefer to stay with the original order, because that way it is easer to see the changes in the source history. There might be situations, when one needs to compare current and older code. I think that staying with the original order is the better solution.
  Gone away and found a better place to stay

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