Asset_contents_paint_ not working in upcoming events asset


(Andrew Harris) #1

Can I please get this confirmed before I go completely insane.

 

%asset_contents_paint_1785092% works in an asset listing, but not in an Upcoming Events Listing. Right?

 

This was my fallback for the ical difficulties I was having - I really need it to work!


(Evan Wills) #2

Hi Woowoowoo

 

I can confirm that you are right. %asset_contents_paint_XXXXXX% does not work in "Upcoming Events Listing%

 

I tried a number of possible variations on "paint" including "layout",  "paint_layout" and "paintlayout" all with no effect.

 

I then tried nesting an empty asset and applying the paint layout to that which caused matrix to totally spit the dummy...

PHP code vomit - http://www.acu.edu.au/admin/evans_test_yard/test ( :unsure: might have to file a bug report about that.)


(Andrew Harris) #3

Evan,

thanks for your efforts!

 

The various event listing assets are really due some love by the squiz devs - it's something of a disappointing mess.

 

Cheers,

Andrew H


(Bart Banda) #4

That bug has been fixed and will be available in the next release: https://squizmap.squiz.net/matrix/8796

 

In saying that, I would also try and use the Calendar Search Page as an upcoming events listing, it has many more features and filtering options so may be better for what you are wanting in general?


(Andrew Harris) #5

Bart,

I found calendar search pages suffered the same issue - couldn't use a paint layout.

 

Creating a good iCal feed is actually pretty hard. There are a few parameters which Matrix outputs routinely which will break a feed if not used carefully.

For example, if an event doesn't have a time component specified it truncates event_start_ical to display only the date, which is fine, but unless the property is then preceded in the feed by a 'VALUE=DATE' the feed is not valid. So, straight away, you have a conditional situation.

 

The other really tricky thing is around assumptions made in the iCal standard regarding event duration.

If a matrix event is from Jan 1, to Jan 3, it's regarded as inclusive - a three day event. But the ical standard assumes it's from 12am on Jan 1, to 12am on Jan 3 - a two day event. Therefore, if a Matrix event is just one all-day event, then it will simply disappear when imported into a calendar, as it has no duration. Tricky eh?

 

On the other hand, iCal can take a duration instead of an end date/time, and Matrix reports Duration correctly, so, you can see why I was suggesting the event_duration_ical keyword as a really neat solution.

 

Lots of fun :-)


(Bart Banda) #6

Yea I always found formatting Icals a pain because the format is soooo picky and needs to be perfect. Conditional keywords are your best friend there and you should be able to cater for each instance using them. Paint layouts applied to calendar search page type format hasn't been reported as a bug yet so if you can successfully replicate it in a recent version of Matrix, let us know and we can investigate further. 


(Andrew Harris) #7

Bart, just tested it in a Calendar Events Search Page, and can confirm, it does not work in that asset either.

v5.3.1.0

 

Cheers, Andrew H


(Bart Banda) #8

That's strange, but we'll check it out and see if we can replicate and report a bug if so. 


(Anthony Ponomarenko) #9

I have been able to replicate and have submitted a bug : https://squizmap.squiz.net/matrix/8847