Forum Replies Created

Viewing 7 replies - 16 through 22 (of 22 total)
  • Thread Starter sbsads

    (@sbsads)

    Here is the output:

    json: {"el_url":"http:\/\/waynedailynews.com\/wdn\/wp-content\/plugins\/event-list\/","el_date_format":"yy\/mm\/dd"}

    conf.el_date_format: yy/mm/dd

    Lines 66, 67 are:

    $json = json_encode(array('el_url'         => EL_URL,
    		                            'el_date_format' => $this->datepicker_format(__('Y/m/d'))));

    I hope that helps. 🙂

    Thanks!

    Thread Starter sbsads

    (@sbsads)

    I changed it to:
    'el_date_format' => $this->datepicker_format(__('Y-m-d'))));

    That did not help, however.

    I did notice something. You have an initial value in the field that defaults to tomorrow and is formatted 2013/12/21. When I click in the field, the calendar pops up, and the date automatically changes to 2013-12-21. I can delete the dashes and retype them, but I cannot type the slashes. The JS validation prevents it.

    I added a mail() line at key points in the process as well, and had the system email me the data submitted. I noticed that the system calls one or the other of extract_date() or extract_date_by_format() three times in the course of saving the data, but I don’t see where it’s called three times. On the successful entries, the extract functions return valid date arrays each time. On the unsuccessful attempts, one of the three will return an empty date array. I think at that point, the script kicks out a false and exits.

    I am curious about the extensive validation procedures for the dates. It seems like a great deal of handling for this data, especially since the form simply fails, dumps the data and returns to the list of events. While I can understand having that were users returned to the form when their date entry did not validate, but it seems that a simpler set of checks might be more useful in this situation, and they would be less prone to encountering trouble in the varied environments users fond themselve (I would expect). What did users run into that make this sort of validation necessary?

    I’m not a master coder, so you probably know something I don’t. Just wondering about the logic behind the code (and maybe I’ll learn something). 😉

    Thanks! 🙂

    Thread Starter sbsads

    (@sbsads)

    If I don’t mess with the date field at all, the event will save. If I change it at all, the event will not save. I attempted to change the Date Format in the General Settings, as suggested in a previous post, but nothing affects the results to this point.

    It looks like you embed the JQuery DatePicker that is in use by WP in general, and perhaps the date validator you use on submission is expecting something different.

    If it helps, this is the compiled line for the date format sent in the form:
    <input type='hidden' id='json_for_js' value='{"el_url":"{ourWebsite}/wp-content\/plugins\/event-list\/","el_date_format":"yy\/mm\/dd"}' />

    Thread Starter sbsads

    (@sbsads)

    I’m using PHP 5.2.17

    The time format is YYYY/MM/DD when I first come into the “Add New” page. When I edit the date, it becomes YYYY-MM-DD. The date chooser does not allow me to edit the time format.

    Thread Starter sbsads

    (@sbsads)

    Oh, and I just upgraded to the very latest WP version: 3.8.
    Still no dice. Exactly the same issue.

    This has nearly a 5-star rating. There must be something simple that can be done to correct the issue. :/

    Thread Starter sbsads

    (@sbsads)

    I really need help with this. I’ve tried to debug, and the system does not even seem to try to insert the new event. I can add a new event if and only if I leave the start date at the default date/time. If I change it in any way, publishing the event fails.

    What would you need from me in order to investigate further?

    I have read other posts where the site-wide date/time settings could be in conflict, but I can’t seem to dial in something that will work.

    What is the trouble?

    Any response would be appreciated.

    Thanks 🙂

    I have the latest of both WP and WP Symposium, and I am still getting a host of errors. Any idea what the problem may be? This should not be an issue (though it may be, depending on the way the plugin was coded), but I did not use the standard wp_ for my table names. Most of the errors I am getting revolve around database issues. Might the prefixes be part of the issue? What other issues could be occurring?

    The site: http://www.videoconnectt.com/vc3/

    One of the errors:

    WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘WHERE meta_key NOT LIKE ‘symposium_%’ AND meta_key NOT LIKE ‘%wp_%’ AND meta_key’ at line 1 for query SELECT meta_key, meta_value WHERE meta_key NOT LIKE ‘symposium_%’ AND meta_key NOT LIKE ‘%wp_%’ AND meta_key NOT LIKE ‘%level%’ AND meta_key NOT LIKE ‘%role%’ AND meta_key NOT LIKE ‘%capabilit%’ AND user_id = ‘1’ made by do_action(‘admin_page_symposium_profile’), call_user_func_array, __wps__plugin_profile

Viewing 7 replies - 16 through 22 (of 22 total)