MODX Staff
This is due to improper positioning and use of the base tag with [(site_url)] as the href, in the default template; it should appear before any other tag that has a src or href attribute, and should then be relied upon to always provide the proper base path of your site. This among other things, helps keep paths in your content consistent, as well as portable regardless of how it is deployed (i.e. in the document root vs. a subfolder). This will be fixed in the new default content, which will be part of the 0.9.5 final release, and addresses several other problems (like improper CSS paths when a page is not found in a virtual subdirectory).
With template ModXHost using SEF urls where the folders show in the url (/blog/blog-post-title.html) the CSS import links are broken. In the other templates it links URLs with
<link title="Light" rel="alternate stylesheet" type="text/css" href="/assets/templates/default/light_green.css" />
In ModXHost it uses
<link title="Light" rel="alternate stylesheet" type="text/css" href="assets/templates/default/light_green.css" />
Which = no style on any page in a directory.
Easy fix on my end, but thought you guys should know.
<!--WEBSITECEO:BEGIN:{764EEF2E-BC11-45CF-8627-300CE1BA2219}-->
<!--
Do NOT modify this script to avoid traffic misrepresentation!
Web CEO 4 0300/1
Code initially inserted into: "/index.php".
-->
<script type="text/javascript"><!--
// hitlens v1.2.7
function hitlens_embedded() {
var id = 126961;
var pc = 0;
var PAGENAME = escape('[*pagetitle*]');
var CONTENTGROUP = escape('[[UltimateParent]]');
var TRANSACTION = escape('');
var TRANSACTION_ID = 0;
var ORDER = escape('');
return "id="+id+"&pc="+pc+"&p="+PAGENAME+"&gr="+CONTENTGROUP+"&tr="+TRANSACTION+"&trid="+TRANSACTION_ID+"&ord="+ORDER;
}
//--></script>
<script type="text/javascript" src="/webceo.js"></script>
<!--WEBSITECEO:END:{764EEF2E-BC11-45CF-8627-300CE1BA2219}-->
« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« Execution of a query to the database failed - Unknown column 'Array' in 'where clause' »
SQL: SELECT sc.parent FROM `carinet`.modx_site_content sc LEFT JOIN `carinet`.modx_document_groups dg on dg.document = sc.id WHERE (sc.id=Array AND sc.published=1 AND sc.deleted=0) AND (sc.privateweb=0) LIMIT 1 
Are you sure that the parse error comes from that tracking code and not from some snippet?
3. Any idea why the following code (WebCEO’s HitLens tracking code) is giving me a parse error? Worked fine on 0.9.2.1. Completely destroys things in 0.9.5 beta 2.
Good point. I’ve been doing more digging and discovered that it’s the UltimateParent snippet in that chunk. Sorry I didn’t catch that before the last post.
Are you sure that the parse error comes from that tracking code and not from some snippet?
This discussion is closed to further replies. Keep calm and carry on.