[bcitweb]

NO that’s all thanks.

[bcitweb]

No it is not networked activated.

[bcitweb]

This reply is private.

[bcitweb]

That is correct – when I follow the Customize link I get a fatal error. I would have reported that as well but only saw it yesterday when I was taking another look at things.

We are also a multi-site installation.

Yesterday I created a new test blog on our network using the twentyseventeen theme. I activated the events calendar and calendar pro plugins to the blog and received the same fatal error when I tried the customize link. I also got the original foreach error when testing the frontend.

Then I disabled the events calendar pro plugin and did not get the fatal error on customize nor the foreach error when I test the front-end.

I then re-activated the pro plugin and the errors came back.

[bcitweb]

And we are also running the latest wordpress, 4.7.2

[bcitweb]

BTW I have updated the calendar plugin to 4.4.1.1

[bcitweb]

Doing a var_dump on the sections array in the above code like this:

private function parse_css_template( $template ) {
    $css = $template;
    $sections = $this->get_option();
var_dump($sections);exit;

Yields the following array structure:

array(7) {
  ["general_theme"]=>
  array(2) {
    ["base_color_scheme"]=>
    string(5) "light"
    ["featured_color_scheme"]=>
    string(7) "default"
  }
  ["global_elements"]=>
  array(0) {
  }
  ["day_list_view"]=>
  array(3) {
    ["price_bg_color"]=>
    string(7) "#eeeeee"
    ["price_border_color"]=>
    string(7) "#c7c7c7"
    ["price_color"]=>
    string(7) "#333333"
  }
  ["month_week_view"]=>
  array(10) {
    ["table_bg_color"]=>
    string(7) "#f9f9f9"
    ["highlight_color"]=>
    string(7) "#21759b"
    ["table_header_bg_color"]=>
    string(7) "#464646"
    ["border_light_color"]=>
    string(7) "#e4e4e4"
    ["border_dark_color"]=>
    string(7) "#d2d2d2"
    ["cell_inactive_bg_color"]=>
    string(7) "#f1f1f1"
    ["cell_inactive_header_bg_color"]=>
    string(7) "#d2d2d2"
    ["cell_header_bg_color"]=>
    string(7) "#acacac"
    ["highlight_color_rgba"]=>
    string(25) "rgba( 33, 117, 155, .75 )"
    ["highlight_border_color"]=>
    string(7) "#14455c"
  }
  ["single_event"]=>
  array(3) {
    ["post_title_color"]=>
    string(4) "#333"
    ["details_bg_color"]=>
    string(7) "#e5e5e5"
    ["details_text_color"]=>
    string(7) "#333333"
  }
  ["widget"]=>
  array(3) {
    ["calendar_header_color"]=>
    string(4) "#999"
    ["calendar_datebar_color"]=>
    string(7) "#e0e0e0"
    ["featured_show_images"]=>
    bool(true)
  }
  ["photo_view"]=>
  NULL
}

The [“photo_view”]=> NULL piece will generate the original reported error (invalid argument provided to foreach) as NULL is not an array.

[bcitweb]

Poking around here. Seeing another error when I go to the Appearance->Customize menu:

Fatal error: Uncaught TypeError: Argument 2 passed to Tribe__Events__Pro__Customizer__Section::register() must be an instance of Tribe__Events__Pro__Customizer__Main, instance of Tribe__Customizer given, called in /srv/pweb/blogs/devel/wordpress/wp-includes/class-wp-hook.php on line 298 and defined in /srv/pweb/blogs/devel/wordpress/wp-content/plugins/events-calendar-pro/src/Tribe/Customizer/Section.php:230 Stack trace: #0 /srv/pweb/blogs/devel/wordpress/wp-includes/class-wp-hook.php(298): Tribe__Events__Pro__Customizer__Section->register(NULL, Object(Tribe__Customizer)) #1 /srv/pweb/blogs/devel/wordpress/wp-includes/plugin.php(203): WP_Hook->apply_filters(NULL, Array) #2 /srv/pweb/blogs/devel/wordpress/wp-content/plugins/the-events-calendar/common/src/Tribe/Customizer.php(487): apply_filters('tribe_events_pr...', NULL, Object(Tribe__Customizer)) #3 /srv/pweb/blogs/devel/wordpress/wp-includes/class-wp-hook.php(298): Tribe__Customizer->register(Object(WP_Customize_Manager)) #4 /srv/pweb/blogs/devel/wordpress/wp-includes/cl in /srv/pweb/blogs/devel/wordpress/wp-content/plugins/events-calendar-pro/src/Tribe/Customizer/Section.php on line 230

[bcitweb]

Hey George;

Thanks for the quick response over the weekend. That did the trick, thanks so much. I swore I replicated every. little. setting. when setting it up on our prod environment, but somehow I missed ticking that checkbox … (face palm) I think I replicated the filters but didn’t go into the type of category filter.

Thanks again, much appreciated.

[bcitweb]

He isn’t the first. We discovered this too and rolled out our own fix. Not sure what CSS our UI dev did, but we got rid of the filter bar obliterating the entries.

[bcitweb]

Thanks George, apologies for missing it. It’s just too bad that the admin UI allows entry of the data and that the list views display it correctly, as it’s easy to miss if you’re not looking carefully at the single view. Could be kind of disastrous for end users on a busy event.

We’ll just either have to list all same-day occurrences in the description for one entry for the day or do each occurrence as a separate entry. Unfortunately, with this event a month away, the ‘coming months’ won’t help this time 😉

Just by way of general feedback, I’d suggest that charging $80 for the pro module when this functionality is borked for our use, is a little disappointing.

[bcitweb]

Thanks Greg, but I think your response misses my point to some degree. It’s not just a lack of communication or a missing feature. If I can enter the data in the admin and it DISPLAYS CORRECTLY on the front end, showing all the recurrences on the SAME DAY, but only opens the first instance no matter which of the recurrences are selected, IT’S A BUG.

If it was just a missing feature, then it wouldn’t be able to do it at all. It’s a bug when the data displayed doesn’t reflect how it’s actually working.

[bcitweb]

That’s a real shame, and a key aspect of what we’re using this plugin for, with regard to this specific event. Perhaps, since it doesn’t support multiple recurrences on the same day of a single entry, safeguards could be placed in the admin UI so that it doesn’t accept the parameters to create them, in the first place. In other words, once I’ve specified a start and end time on a given day, adding new times on the same day should be prohibited.

I guess the best we can do is create a single all-day entry for each day and then include all times in the description, or create multiple unique entries. The only problem with the latter approach is that it makes using the recurring events list feature incomplete, since users looking at that won’t see all occurences.

[bcitweb]

All repeating events link to a url like events/recurring-event/yyyy-mm-dd/ and only the first event for the recurring event shows, regardless of what link we follow in the events/recurring-event/all list.

Maybe the name of this thread should have been a question, “Do single-day repeating events work?”

[bcitweb]

Very nice. Thanks.

[Author]

Posts