0.9.5 Public Beta 3 support

• • 
  • 59 Posts
  milicicd Reply #171, 20 years ago

  rev 1717
  
  Issue1:
  I have a problem with QuickEdit. My site uses friendly URLs with friendly aliases, friendly alias paths, allowed duplicated aliases. QuickEdit is working nice on pages of first level (www.site.com/page.html).
  However, when going deeper into structure (www.site.com/folder/page.html), QuickEdit is not even displaying properly anymore.
  Upon inspecting HTML source, I discovered this chunk
  
  

  <!-- Start QuickEdit headers -->
  <script type="text/javascript" src="/manager/media/script/scriptaculous/prototype.js"></script>
  <script type="text/javascript" src="assets/modules/quick_edit/javascript/Cookie.js"></script>
  <script type="text/javascript" src="assets/modules/quick_edit/javascript/Drag.js"></script>
  <script type="text/javascript" src="assets/modules/quick_edit/javascript/moo.fx.js"></script>
  <script type="text/javascript" src="assets/modules/quick_edit/javascript/QuickEdit.js"></script>
  <link type="text/css" rel="stylesheet" href="assets/modules/quick_edit/styles/toolbar.css" />
  <!-- End QuickEdit headers -->
  

  
  
  Obviously, the problem is with "assets" lines starting without "/".
  How can I solve this?
  
  Issue2: After upgrade completed, I got standard warning about config.inc.php being writable. After correcting it, "Configuration check" on Configuration tab still contains orange warning triangle without any text following it
  
  Issue3: When inspecting System events, I have "parse error". Upon clicking on [Copy SQL to ClipBoard], IE reports error [’holdtext’ is undefined] on line 140, char 17
  
  Question1: If all nodes in site tree have context (i.e. right-click) menu, why is site root different? If I want to create document on root level, I must go to Site -> New Document , instead of simply clicking on root and selecting "create new document/folder here".
  
  Question2: I noticed my System Events is getting rather big as time passes. After about month of ModX usage, MySql table with events grew up to 58Mb! Is there any option to limit its size to something like "no bigger than" or "no more than xxx latest events". Could this make my site slower if I forget to purge this table from time to time?
  
• • 
  • 45 Posts
  ram Reply #172, 20 years ago

  Re: issue 1 (^above)
  
  The code for the quick edit headers can be found at line 222 of the file:
  
  /assets/modules/quick_edit/output.class.inc.php
  
  I think that either adding an initial slash in the src attributes in output.class.inc.php should do the job here or add a create a plugin to insert slashes with the onWebPagePrerender event.
  
  I believe that some parts of the MODx setup use the <base> element to get browsers to resolve relative links (I like the slash myself).
• • 
  • 59 Posts
  milicicd Reply #173, 20 years ago

  Regarding "slashing"
  
  When referencing from root (1st level), relative and absolute path are always the same ("assets" == "/assets").
  So, adding initial slash in the src attributes would make no difference for urls of type index.php?id=
  and problem with friendly URLs would be solved.
  Can we make "slash" version default one? And more general, in all places in ModX where "assets" is referenced, can we make it starting with slash - since assets is always placed in site root?
  
• • 
  • 66 Posts
  bkvernst Reply #174, 20 years ago

  Version: Beta 3 rev. 1533
  Running on: Apache
  SEO URLs: Off
  Type of error: A bug?
  Where: Manager > Tools > Configuration > Miscellaneous settings > Manager Theme
  Affects: The whole manager
  
  Description:
  Even though we’re not "supposed" to, I chose to change the manager theme from MODx Light to MODx, just to try it out, which resulted in expected layout trouble, even though it seems that it can hardly read the CSS file at all (see the attached screen shot), but I’m also completely unable to change it back. Even though I’m choosing MODx Light from the ’Manager Theme’ option box and saves, most of the design seems to have trouble returning to normal.
  Some of the buttons and icons changes back to MODx light, along with the whole manager log in page, but most of the manager are still in MODx style.
  I’ve tried to refresh, log in/out several times, recache (just to be sure), without it giving any effect at all...
  
  Was this bug submitted already? I couldn’t find it in the tracker...?
• • MODX Staff
  • 1,535 Posts
  Garry Nutting Reply #175, 20 years ago

  Even though we’re not "supposed" to, I chose to change the manager theme from MODx Light to MODx, just to try it out, which resulted in expected layout trouble, even though it seems that it can hardly read the CSS file at all (see the attached screen shot), but I’m also completely unable to change it back.

  Heh, you know when we advise not to do something ... we do actually mean it.
  
  Have you changed your manager user settings by any chance after changing to the MODx theme? In this version of the beta, it saves the manager user theme value along with any other manager user settings - this will override the site configuration setting. So, check what that setting is and change it back to MODxLight if needed.
  
  Other than that, can’t really think why it’s not changing back to MODxLight theme. If you have SVN, you may want to upgrade to the latest MODx revision as the themes are all sorted out and you won’t have the styling problems that are present in rev.1533.
  Garry Nutting
  Senior Developer
  MODX, LLC
  
  Email: [email protected]
  Twitter: @garryn
  Web: modx.com
• • 
  • 1,193 Posts
  ScottyDelicious Reply #176, 20 years ago

  Quote from: JeremyL at Oct 13, 2006, 02:41 PM

  
  Bug or just missing feature?
  
  When I create a page and select meta tags / keywords they get inserted into the page. But if I go back to edit the page, I cannot tell what meta tags or keywords where selected in the manager. When I go back later they are no longer highlighted. Is that how it’s supposed to be?
  

  
  It’d be nice to get those into checkboxes.
  Husband, Father, Brother, Son, Programmer, Atheist, Nurse, Friend, Lover, Fighter.
  All of the above... in no specific order.
  
  I send pointless little messages
• • MODX Staff
  • 10,725 Posts
  opengeek Reply #177, 20 years ago

  Quote from: milicicd at Oct 14, 2006, 08:11 PM

  
  Regarding "slashing"
  
  When referencing from root (1st level), relative and absolute path are always the same ("assets" == "/assets").
  So, adding initial slash in the src attributes would make no difference for urls of type index.php?id=
  and problem with friendly URLs would be solved.
  Can we make "slash" version default one? And more general, in all places in ModX where "assets" is referenced, can we make it starting with slash - since assets is always placed in site root?
  

  Absolutely not. assets !== /assets. This is only true if your MODx site is installed in your document root.
  Jason Coward
  Chief Architect @ MODX
  http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek
• • 
  • 59 Posts
  milicicd Reply #178, 20 years ago

  I agree. Adding simple
  
  

          <base href="http://www.domain.com/">
  

  
  
  in head section solved this (and some other potential) problem.
• • 
  • 141 Posts
  zenmaster Reply #179, 20 years ago

  I am attempting a clean install of the beta.
  
  I have created a new database, verified that it is empty, and tested the connection.
  
  I then see the following:
  
  

  Setup has carried out a number of checks to see if everything’s ready to start the setup.
  
  Checking PHP version: OK!
  
  Checking if sessions are properly configured: OK!
  
  Checking if assets/cache directory exists: OK!
  
  Checking if assets/cache directory is writable: OK!
  
  Checking if assets/cache/siteCache.idx.php file is writable: OK!
  
  Checking if assets/cache/sitePublishing.idx.php file is writable: OK!
  
  Checking if assets/images directory exists: OK!
  
  Checking if assets/images directory is writable: OK!
  
  Checking if assets/export directory exists: OK!
  
  Checking if assets/export directory is writable: OK!
  
  Checking if manager/includes/config.inc.php exists and is writable: OK!
  
  Creating connection to the database: OK!
  
  Checking table prefix `modx_`: OK!

  
  So far, so good.
  
  However, when I select "install now" I get an error message
  
  

  Setup will now attempt to setup the database:
  
  Creating connection to the database: OK!
  
  Selecting database `modx`: Database selection failed... The database does not exist. Setup will attempt to create it.
  
  Creating database `modx`: Database creation failed! - Setup could not create the database!
  
  Setup could not create the database, and no existing database with the same name was found. It is likely that your hosting provider’s security does not allow external scripts to create a database. Please create a database according to your hosting provider’s procedure, and run Setup again.

  
  The name of the database is not "modx" and can never be as my ISP adds a prefix to the database name and I cannot rename it.
  
  Any suggestions, please?
• • MODX Staff
  • 1,535 Posts
  Garry Nutting Reply #180, 20 years ago

  I’ve got a fix in my personal SVN branch for this ... just needs merging with the main trunk.
  
  In the meantime, in install/index.php - run a search for all occurrences of databasename and replace with database_name. There’s about three in total.
  
  That’ll fix the issue.
  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.