Custom template vars for MODx Evo

hi

:) actually, i’m more of a moo guy than a jquery one (even if i often have to make websites with jquery...) and, upgrading moo 1.12 classes to moo 1.3.2 ones sounds better to my ears

you know, i love classes... now i must admit jQuery UI has set their oo writing a little upper and offers great UI abilities (moo + mocha ui of jxlib aren’t that bad either even if some things would have to be rewritten to work with moo 1.3+)

well then, why not, lets consider that too

Have swing

@ didko,

the picture you’re sharing looks normal those fields are not filled natively, MODx has an internal set of dates to manage ressources, those are for you if you needed to pusblish a ressource later or unpublished it automatically on a forecast date (be careful with those dates, check if your server internal date/hour matches your timezone when using them...)

have swing

Hey virtualgadjo,

not a js dev her, so i’m not really savey on that topic, just thought it might be good to use jQuery because addons/extensions in the backend are more likely to be developed with it, but then again, i might be wrong!

thanks & chapeau for your enthusiasm to keep Evo alive!

@virtualgadjo

The problem is that there is no a calendar popup to pick your date

hi again (music for me today )

@ ditko, too bad, in this case your running into those compatibility problems "old" releases of any js framework have with new browsers... i know another one with tinyMCE link and files manager popup and chrome...

@ sharkbait, you’re probably right, most of the extensions must be written written with jquery... but, in some way it icould be easier to have the backend written with moo and add extension written with jquery in compat mode. Having, let’s say jQuery 1.6.2 as the backend js framework could also be a problem with extension written with an older release. (something i’ve ran into with a website written with jQuery on the front end and using colorbox as the modal window plugin, when connected to the manager i had conflict between the jquery and colorbox used for quickmanager... i eventually disabled as i do not use it)
Whatever the choice is going to be (mootools/jquery or, why not, dojo, a great UI framework too even if abit slower than moo or jquery), we will not be able to avoid all the possible conflicts but namespacing MODx backend js will help getting rid of a lot

now when it comes to my enthusiasm, i’m the one who has to thank you! MODx is such a great tool the least i can do is to help as much as i can keeping alive forever being a js freak i thought it was a domain i may help a little

Have swing

it seems to be the case of MultiPhotos tv...
too bad, actually, with MODx backend you’ll have to deal with some restrictions in ie9 due to a little old moo release in use...

I fixed ie9 bug (MultiPhotos 1.2.3)

@ didko,

Are you using IE9. I see the same problem... lack of datepicker.

It seems to be an IE9 mootools 1.12 bug. I tried upgrading the manager mootools which fixed it but broke the site tree.

In the end I edited /manager/index.php
Around line 67 it sets compatibility mode. I change IE from edge to ie8 and this fixed it:


If you use quickmanager on the frontend you may want to add a line to your site header:

@ uxello

When you upgraded mootools did you combine the core and the more?
The amount of IE9 users are growing and I love working with Evo so I want to upgrade the Mootools to solve the datepicker Issue

@kaiji_nl

I just used the default latest mootools.

The problem is the mootools 'Ajax' call in mootools 1.x is depreciated in later versions of mootools. I did start to go around replacing all the Ajax calls in the tree.php file and did get the tree working. However there are other depreciated calls scattered throughout the ModX manager and it was getting way beyond a simple fix... hence the forcing of IE8 instead!

Well, there is a group working to clean up Evo, and among other projects in the works is converting the Manager to use JQuery instead of MooTools.

In any case, it really doesn't affect the native custom TVs in Evo 1.0.5+, as you can use whatever libraries you please.
[ed. note: sottwell last edited this post 13 years, 9 months ago.]