MODx9.1 Todo

The following minor changes should be made before 0.9.1 according to the bugtracker:

http://modxcms.com/bugs/task/56

http://modxcms.com/bugs/task/132

http://modxcms.com/bugs/task/124 (Tagged for 0.9.1 by Ryan)

I’m doing some testing in FF, and would love to see some bug/JS errors dissappear. For instance, when logging in and going to the homepage, I get the following JS error:

Error: parent.rpcLoadData is not a function
Source File: http://blah.com/manager/index.php?a=1&f=3ldr&indent=1&parent=0&expandAll=2
Line: 1

When going to edit a page:

Error: top.scripter.work is not a function
Source File: http://blah.com/manager/index.php?a=2
Line: 30

Also, we need to make sure that upgrades install the plugin / module params for QE properly that Adam added.

Not a lot of "real" stuff to do not related to oversights discovered during internal testing:

Only one Bug outstanding

Just a few To Dos

The most "interesting" bug remaining is:

The API functions regClientStartupScript and regClientScript don’t work with uncached snippets (called with [! !]). Just nothing happens. When I change the snippet call to [[ ]] it works just fine.

I tested it with the following snippet (simplified from examples in the docs):
$src2 = "<script type=’text/javascript’>
alert(’Hello’);
</script>";

$modx->regClientScript($src2);

Anyone have an idea?

The most "annoying" To Do that somehow slipped under the radar for a long time:

Is there going to be a better way of setting dates in MODx?. Its slow enough having to set the expiry date of an account for 14 months time, but setting the birthdate of a new user is painfully slow.

If you were born in 1955, it takes 50 mouse clicks just to change the correct year, then do it for a dozen new users, and I need to buy a new mouse  Smiley

Can the calender have some sort of drop down selection for the year, and even months would be good. Otherwise I’d rather type it in myself which MODx won’t let you do.

I think all we need to do is just turn off the input-field-disabled state there, but I don’t see where/how to do that easily in the source. Any help available?

P.S.
And with fixing these two and another round of testing, I think we can release 0.9.1 into the wild.

The date thing is around line 646 of manager/actions/dynamic/mutate_content.dynamic.action.php, FYI.

It looks like it’s hiding the actual input field and turning the span id="pub_date_show" into a faux input box. If this is a correct assumption, I think I’ve got a quick fix!

And so it appears it does work that way... look for commit #592...

That leaves one bug and some internal testing as the remaining 0.9.1 issues to resolve for its release! Need some help on that bug, folks...

Quote from: rthrash at Dec 11, 2005, 08:52 AM

The most "interesting" bug remaining is:

The API functions regClientStartupScript and regClientScript don’t work with uncached snippets (called with [! !]). Just nothing happens. When I change the snippet call to [[ ]] it works just fine.

I tested it with the following snippet (simplified from examples in the docs):
$src2 = "<script type=’text/javascript’>
alert(’Hello’);
</script>";

$modx->regClientScript($src2);

Anyone have an idea?

Ryan; I believe this is just a misunderstanding. You cannot pass Javascript source code to this function --> you must provide a valid src attribute for the script, the code for which should be in a separate file that can be referenced by the src attribute.

I’ve passed it source before, the function has these lines that will accept either just a source filename or an entire block of script. But I don’t know about the [!...!] vs [[...]] issue.