MODx 0.9.7 alpha 2128 (Known Issues and Suggestions)

I just thought of something, and it is not directly related to the 0.9.7 core, but this is the base of a new release and I would love to see this thing nipped in the ass before it goes past 0.9.7 alpha. Ever since TechPreview 3, I have been modifying the weblogin snippet and taking out that stupid javascript that put’s the focus on the #username input. Am I the only one that finds this to be a pain in the ass? I always use a side bar login in my templates, and when navigating pages, I make frequent use of keyboard navigation (space bar to page down, down arrow to scroll down, up arrow to scroll up, command + up arrow to return to top). This totally screws that up because first I have to click twice somewhere on the page, making sure it is not a link, just to get the stupid focus out of the form input! Are there a lot of folks that would miss this? Or, as a comprimise for those who rely on this functionality, is there a way we can make this optional so I could put &focus=`false` or something in my WebLogin snippet call? Like I said, this has bothered me (and I have deleted it) since the tech preview days.

-sD-

Awesome news! I contacted my hosting company’s customer service department to have them add pdo_mysql.so to the extensions, and in seriously <15 minutes I am up and running... er... generating errors.

I followed garry’s advice and commented out the session_set_save_handler arrays, not too sure how bad this is yet, but things seem to be working. I am off to make some pages and break some cages!

-sD-
Dr. Scotty Delicious, Scientist.

Quote from: TobyL at Dec 22, 2006, 08:00 PM

I must say I don’t understand half of what you’ve done Jason (but I’m sure I’ll get there in the end). Excellent work.

I did a fresh install on winXp sp2, mysql 5.0 and php 5.2.0 without PDO extension - All very smooth! Added the php PDO extension and again all seems to work as intended (possibly even smoother )

However, when I browsed through the demo pages I came across an anomaly in the Contact Us page. The page displayed and extra `]] at the top of the page. Have a look yourself. The page has 2 snippets, the old contactform and eForm. hen deleting the old contactform snippet the problem goes away.

After experimenting a bit I figured out that adding snippet calls to a page can produce unexpected results when saving as well:

[[snippetName? &param=`value`]] 

Saves fine.

[!snippetName? &param=`value`!]

Saves fine.

[[snippetName? &param=`value`]] 
[!snippetName? &param=`value`!] 

Saving not Ok.. ends up like last ] stripped i.e.:

[[snippetName? &param=`value`]] 
[!snippetName? &param=`value`! 

It should definitely work smoother with PDO, considering I wrote a PDO emulation layer that works in PHP 4 and 5 when PDO is not installed and configured. If I can find a way to use my PDO emulation when the requested PDO driver is not available, that would be even cooler, but so far, that’s not looking like a good possibility...

As for the wierd content on the contact page, this is just the default content from 0.9.5 and will be completely replaced very soon, by content that is coded specifically for the new simplified tag format. All tags for the new parser are now [[ ]] with the kind of component determined by the first few tokens in the string:

[[snippet]]
[[!nonCacheableSnippet]]
[[$chunk]]
[[*tvsAndResourceMeta]]
[[!*nonCacheableTV]]
[[!#*nonCacheableTVwithQE]]
[[+placeholder]]
[[++configSettings]]
[[~links]]

Legacy tags are converted to this format as the content is parsed.

And yeah, I’m not really sure what is going on with saving, but I have all kinds of code being stripped when saving it through this version of the manager. I’ll bet anything it is related to the fact that the manager is running on the new MODx core and possibly applying the front-end request cleansing to the back-end. I’ll dig into that more today.

Quote from: OpenGeek at Dec 23, 2006, 12:07 PM

And yeah, I’m not really sure what is going on with saving, but I have all kinds of code being stripped when saving it through this version of the manager. I’ll bet anything it is related to the fact that the manager is running on the new MODx core and possibly applying the front-end request cleansing to the back-end. I’ll dig into that more today.

Found this problem and a few others and have committed the fixes. I’ll upload a new build as a Christmas present, and this should address most of the issues we’ve run into so far, so I’ll start a new thread for the new package.

Nice Jason, thanks and Merry Christmas !