Ability to use only the first date. in a date range.

After an upgrade to 1.3 (on Modx 2.5.1 or 2.5.2) the TV is not working as it should be, no extra fields are shown in the TV and also the other TV's are influenced. After uninstalling daterange the manager of Modx doesn't start up (white page). Error log: (ERROR @ /data/sites/web/nameofsite/www/core/xpdo/xpdo.class.php : 643) Could not load class: DaterangeTV from daterangetv.
(ERROR @ /data/sites/web/nameofsite/www/core/xpdo/xpdo.class.php : 1259) Problem getting service daterangetv, instance of class DaterangeTV, from path /data/sites/web/nameofsite/www/core/components/daterangetv/model/daterangetv/
I had to manually copy the files from github into the component directory to get back access to the manager.

Hi and thanks for your plugin!

Do you think it can be used with DateRangePicker (http://www.daterangepicker.com/#examples) in order to filter GetResources (https://rtfm.modx.com/extras/revo/getresources)?

Thanks for your answer.

Regards,
Carlo.

I'm getting a "This field is required" even when I have it set to Allow Blank.

Hi,

after upgrading yo 1.3.1-pl3, my daterange TVs don't show anymore.

After some debugging I found that the daterange fields don't show if allowBlank is set to NO. They do if it's set to YES.

Here is what I found in the manager html source of a resource with a daterange tv:

allowBlank set to false:
...

<script type="text/javascript">
    // <![CDATA[
    Ext.onReady(function () {
        MODx.load({
            xtype: 'daterangetv-combo-daterangetv',
            tvId: '17',
            daterangeFormat: '' || MODx.config['manager_date_format'],
            allowBlank: ,
            daterangeStart: '',
            daterangeEnd: '',
            endTV: '',
            renderTo: 'modx-daterange-tv17'
        });
    });
    // ]]>
</script>

...

allowBlank set to true:
...

<script type="text/javascript">
    // <![CDATA[
    Ext.onReady(function () {
        MODx.load({
            xtype: 'daterangetv-combo-daterangetv',
            tvId: '17',
            daterangeFormat: '' || MODx.config['manager_date_format'],
            allowBlank: 1,
            daterangeStart: '',
            daterangeEnd: '',
            endTV: '',
            renderTo: 'modx-daterange-tv17'
        });
    });
    // ]]>
</script>

...

I see it being super useful for using a daterange for events that start at (for example) 8pm on a monday and run until 10pm on Wednesday. This would be a great enhancement.

If I enter in a date such as 02/12/2020-02/15/2020 in a collections child, when I view the collections grid (with the column set up with a daterange renderer) the dates appear as 11.-14.February 2020.

So I know:

1. The dates are rendering proper format according to the tv
2. The input is being read by the tv
3. The input is being rendered by the collection grid properly
4. I messed up somewhere (or there is a setting that I'm missing hopefully)

I tried turning on the debugging mode and did not get anything helpful, other than I had the wrong locale value. Fixing that has not fixed my issue.

I'm sure this is something dumb and it's staring me right in the face, but for the life of me I can't figure it out.

I can provide screenshots if that helps, too

DaterangeTV is still broken after update from 1.2.3.

In combination with Migx the daterangeTV breaks down the Migx. You can't give in a date and the other fields are corrupt.

My clients wants the year on both the from and to even if it's in the same year. How would I do this.

ie.....August 25, 2015 to December 08, 2015