0.9.5 test builds

bugs I found in MODx 0.9.5 beta (rev 1325)

In IE the context menu for the document tree gets scrollbars and a small box  instead of the compleat menu rev.
Tiny needs an update I gat a problem when I set the language to dutch this big is already fixed in the lates release by Bravado.
after a clean instal I get this error on the top of my page (minimaltemplate standard instalation page)

Notice: Undefined index: mgrValidated in /home/httpd/vhosts/hilverda.eu/httpdocs/index.php on line 138

Thats it for now

Question on the manger page for weblinks:

Is there a reason there is a "Searchable" checkbox on this page? I suppose you could search for the page title... but still...

Hi David,

Sorry about the late response.

I’ll also double check on the conditional tags but here are some basic examples of how these tags can be used.

In short you can use the IF-ISSET to test if the value of a of a tag has been set. It’s similar to the PHP isset() function:

[[:IF-ISSET? &value=`[[+ShowContent]]` &then=`Here’s my content` ]]

You could use a snippet to set the value of the ShowContent placeholder.

Another example where this tag might come in handy is in the case where you might want to use a TV to hide or show some content on a page. The TV could be a simple checkbox:

[[:IF-ISSET?
&value=`[[*ShowContent]]`
&then=`Some extra content here. This could be a sidebar, etc`
&else=`Default content here`
]]

The IF-EMPTY tag is the opposite of IF-ISSET. It checks to see if tag or value is empty then displays some content. This tag is also similar to the PHP empty() function:

[[:IF-EMPTY?
&value=`[[*Private]]`
&then=`You can’t see this section`
&then=`Hi and welcome to my private corner`
]]

The IF-COMPARE tag is used to compare the value or content of two tags. This is very useful if you would like to display some content when a tag contains a certain value:

[[:IF-COMPARE?
&value=`[[*Options]]`
&equal=`1`
&then=`You have selected Option 1`
]]

[[:IF-COMPARE?
&value=`[[*Height]]`
&equal=`[[*Width]]`
&then=`Display something here`
]]

By combining these tags a user can control where and when content is displayed.

Some other examples where conditional tags might come in handle:

* Dynamic CSS pages - render CSS based on browser
* Mobile Pages (WAP Content) - display device specific content
* Restricted Content
* Render Browser specific content - great for serving up IE bug fixes
* Basic Content scheduling - example:

[[:IF-COMPARE?
&value=`[[Date]]`
&equal=`2006-08-25`
&then=`Welcome to our One Day Sale!...`
]]

Surely all the DropMenu issues will go away when it is switched to Wayfinder?

Quote from: rthrash at Aug 24, 2006, 09:17 AM

Is there a reason there is a "Searchable" checkbox on this page? I suppose you could search for the page title... but still...

Weblinks might be internal - if I had a weblink to a forum, I’d expect it to turn up if I searched for forum. People are strange and will search for anything even if there’s a big bright orange button with the exact same word they’re searching for. Regardless of whether it actually works with the default search snippets, I wouldn’t like to see that checkbox go.

Quote from: davidm at Aug 23, 2006, 11:41 AM

What I could do is give a go at trying out the new tags in the context of the "sample content" bundled with MODx, which would make it easier for everyone to re-use. In fact, that’s not a bad idea. I guess MODx users will need some samples of what can be done with the new parser, would be great to have this added to default content, no ?

Thanks david and xwisdom for the conditional tags examples. And yes, some examples in the default content code would be good - particularly as that default content gets showcased on OpenSourceCMS.com. The IF-GROUPS could replace the snippet that is being used to check if someone should be able to see the Add Blog Entry.

Actually, I’d (ultimately) like a section on MODxCMS that explains how each page of the default content is done and why etc, and possibly briefly outlines other ways that could have been achieved. This would answer a lot of forum questions from people who have deleted the default content.

Thanks Raymond that’s just what I needed to get a grasp !

This really is amazing, using those tags to test placeholders or TVs, I mean there will be so many possible use it’s so g-r-e-a-t !

I’ll get down to work on this, having the new tags integrated to the default content, I’ll try to squeeze that into my currently tight schedule...

Quote from: xwisdom at Aug 24, 2006, 10:01 AM

Hi David, Sorry about the late response.

(...)

I’ll also double check on the conditional tags but here are some basic examples of how these tags can be used.

(...)

Some other examples where conditional tags might come in handle:

* Dynamic CSS pages - render CSS based on browser
* Mobile Pages (WAP Content) - display device specific content
* Restricted Content
* Render Browser specific content - great for serving up IE bug fixes
* Basic Content scheduling - example:

(...)

I was playing around with a few sample snippets on my local test site earlier and I miscommented a line in the snippet - when I viewed my frontend site, every page was returned completely blank. As soon as I corrected the error, everything was back to normal.

The parser class seems to fail at the point it includes the ’siteSnippets.cache.php’ if there are any errors in the snippets - I’m not sure if there’s much that can be done for this but just something to remember if we start to get any ’blank page’ support threads when 0.9.5 goes live.

(my setup: MAMP, Apache 2.0.55, PHP 5.1.4, latest SVN build)

EDIT: there is also the possibility that it’s something to do with my setup ... I’ve tried all manners of error suppression but it still bombs out on me, the snippet in question was only referenced on one page of the site so I’m just not sure what’s going on really.

Actually, I’ve had it go mad a few times, and that was with default snippets. If I edited the cache file to take out the gnarlsed-up snippet, all was well. It is not doing it on a more recent build, touch wood.

In other news, is there any chance of merging web_users and web_user_attributes for 0.9.5?

Quote from: PaulGregory at Aug 24, 2006, 07:40 PM

In other news, is there any chance of merging web_users and web_user_attributes for 0.9.5?

I don’t think that’s a good idea just yet. The structure of user identity, IMO, should be kept isolated into three sections, which should be represented by individual classes/tables. These are sections are, credentials/authentication, profile/attributes, and access/permissions, and we already have a close approximation of that model with our current structure (despite the manager/web user chasm). However, I do think some of the credentials-related columns now in user_attributes (a.k.a. the profile class) could possibly be moved to the appropriate user or user_settings tables; things like blocked at least, though I really think each individual column deserves some discussion before we decide where to move anything, since that will likely affect all kinds of legacy deployments, and prevent many core snippets from working without some potentially non-trivial revisions forced on would-be upgraders.

I also want to keep this division moving forward because I have a plan to allow the MODx user framework, to be able to serve as a central source of identity which can aggregate data for each of the three classes of data I mentioned, from whatever repository it is possible to get that data from. Identity data that other applications can then interact with in whatever imaginable way they need to (PHP via MODx API, direct to database from some other language, an Ajax service that returns SAML, or a JSON equivalent, a SOAP service, etc.). This approach of aggregation avoids the need for bi-directional synchronization, and can even allow centralized management of user data if the foreign repository can be written to from MODx. And either the local application continues to have control over it’s standard user system and cares nothing about the MODx aggregation going on, or a bridge can be implemented from the application to take advantage of it.

I’ve started a new thread with my reply to the user stuff, as it is clearly an issue to return to post-0.9.5.
http://modxcms.com/forums/index.php/topic,6712.0.html

Have any of you tried regClientScript and regClientStartupScript functions with 0.9.5? I just had a support request for GoogleMapMarker snippet. I viewed the site url and it seems that the regClientScript has gotten executed twice and regClientStartupScript not at all. I asked for login details from the user and just peeked her manager. She uses MODx 0.9.5 (rev 1288). I don’t know if she understands that it’s still in developement and I adviced to use 0.9.2.1. But anyways, could someone try GoogleMapMarker on your 0.9.5 installs (I havent installed it yet ) and see if you get same results.. Or just try to do something with the regC...functions.