Glad you are happy with it. See http://icalevents.anmari.com/1789-border-and-spacing/ for css help – i used your site as a case study.
Thank you, AnMari
for the concise study.
In fact I have already made changes to the calendar, but changing the css of the theme.
You can take a look here: http://testas.klajoklis.lt/wordpress/?page_id=181
but now I will be able to make it even more beautiful 🙂
BTW, you could probably know this:
Is there any other text field in google calendar (exceept for Subject and Description) that would be possible to import as CSV file.
I just need one more text field (shame google for not implementing categories)
Looking good – let me know when you are done and I’ll add it to the showcase – most tailoring of widget I have seen so far.
Not sure what you mean by import as csv, but no there do not seem to be any other fields.
What may be of interest to you is that I am working on a complementary plugin which will allow one to create events in wordpress and generate an ical file so that it can be read by other calendars as well as used by this plugin. It will use posts and post categories and the custom fields and so I will try to incorporate as much of the ical spec as possible – and of course the categories will be there.
I will look forward to seeing this new plugin, as ical can hold much more information. I will definitely be the user uf it.
The billiards season starts tomorrow, and I have so many pages to fill 🙂
I hope I will come back to the calendar in couple of weeks.
BTW, I couldnd find any description of the new realease. What was changed in particular.
Because I have noticed that the fields Before and After sometimes just do not work. They accept tags like <H3>, <p>, <strong>, but they dont seem to accept <b> or <i>, or <center>, or <font color="red">, or <p style="...">.
Thank you again
See changelog for what was changed: http://wordpress.org/extend/plugins/amr-ical-events-list/changelog/
Re before and after:
Yes – thank you for raising this as I realise that it is not documented and I will rectify that. There is a reason:
I am very keen on
1) clean semantic xhtml and on having my code validate. much time was spent on ensuring that even the admin pages validate (xhtml and css), and
2) separation of html and styling. Keep the code semantic and style it using css. Many css tags have been provided to facilitate styling of the event data. each ical field has it’s own css tag EG: to style the summary in red, add css for li.summary etc to either a custom css file for the plugin – see the settings or to your theme.
The plugin thus strips all tags (using php function strip tags) except for the following
<p><br /><hr /><h2><h3><h4><h5><h6><strong><em>
So,
use < strong > instead of < b >
use < em > instead of < i >
if you want the font red bit to be consistent with a heading in your theme – use the relevant < h > tag.
