I took a look at this and it was due to a stray bit of CSS code that should not have been in the list view template.
Version 2.2.0.1 is a fix for this issue. It will be available to download shortly.
Oh waw! I found it weird but indeed, but then a phone_only makes it obviously evident. Thanks!
Always happy to help a fellow clarinetist. 😀
Hi room34
I’m still having exactly the same issue with the latest release 3.2.0
Is there a fix for that in the pipeline or do you have a css workaround for that?
best regards,
I haven’t had a chance to troubleshoot this yet but I think some of the changes in the newest version may be resulting in some caching issues, either on your local device or on the server.
First, try clearing the cache in your web browser. If that doesn’t resolve the issue, it may be due to bad data cached in the WordPress transients. You can purge the transients by adding reload="true" to your shortcode.
Let me know if neither of these resolves the issue for you.
thanks for the speedy response!
i tried this but it did not work…
Nevertheless i found a workaround its quite stupid but it works
I added the attribute toggle=”true” and the custom CSS
.ics-calendar.toggle .event .descloc {
display: block;
}
to match the same condition in CSS as if you would have clicked the event in the list. So the location is always shown.
anyway I assume the solution would be to add a new attribute which only affects the list view e.g. loclist=”true” with more or less the same as toggle but without the click function.
Ah… OK, I think what happened here was an oversight/mistake on my part. I hadn’t accounted for situations where the location might be displayed but the description is not. By wrapping the two together into a single container block and applying the eventdesc logic to that container, I’m hiding the location and I shouldn’t be.
I’ll have this fixed in the next update.
I just tested this and it does appear to be showing both the description and location properly, as long as you have location="true" set in the shortcode. The changes in version 3.2.0 do require you to clear your browser cache though. Are you sure that’s not the issue?
