Previous versions please?

Hey @juliepayne76,

To answer your question about previous versions, you can find us on github, and specifically if you are looking for downloads of previous versions, you can find most of them on the releases page now. That being said, it sounds like you have a few questions here that are leading you to believe that the current version on WP.org is not the stable version. In fact, the one that is on WP.org is the current stable version. Let me address your questions to clear up any confusion.

You published an event, but it did not show on your calendar page. This could be caused by a number of things, most of which are covered in the video you mentioned. The most common problems that usually occur to produce this outcome, is understanding that the child events can be (and must be) individually published or unpublished. During the event creation process, in the ‘Event Settings’ box (below the calendar), when you select the settings for each of the child events (or all at once, since you can select multiple at a time), double check that the ‘Status’ is set to ‘Published’. If it is not, change it to published and save the parent event. Next double check that the ‘Visibility’ of the child events are set to ‘Public’. There are various visibility levels, each allowing distinctive groups of users to see an event, ‘public’ being the one with the most access allowing the most users to see it (which is the only one that allows logged out users to see it). If those things are not the problem, then we may need to go through additional troubleshooting steps to figure out why they are not showing for you. Let me know if we do.

The Datepickers all use the date format specified in the loaded language translation file. Currently, en_US is the only English variant that is included with the software. Using a tool called POEdit, you can create a language translation file for en_GB (UK), and change the data formats to match what they should be for the UK (as well as any other language changes). If you do that, perhaps you would be willing to share it with the community, so that others in the UK could have proper date formats. If that interests you, email the resulting PO and MO files to info@opentickets.com, and we will get that added in. It is up to you, but this is how the datepicker formats get changed, the language files. And the community thanks you in advance, if you decide to make a UK translation file.

As for the Calendar page, that one is a bit more tricky. Each theme is different in the way that it defines the layout of the page. The plugin itself handles the formatting needed to make the calendar visible in at least the core WP themes and in the ‘Canvas’ theme, a WooThemes theme. It does however add the ability to define your own calendar page template, which gives you the power to change the ‘shell’ of the calendar, so that the calendar fits nicely in your theme. I described the basic process for this as an answer to the same question for a different theme, a while back. The steps are basically the same, but the specific changes I tell him to make would likely be different for you. If you can provide me with a link to your calendar, I could probably point you in the right direction of the potential changes you would need to make.

I am about to release a new version in a few minutes; however, it only provides the addition of the German translation, graciously provided by H.T. (@ht-2). I would do similar for the UK translation once it becomes available. Hopefully, these answer your questions. If you really need to try an older version, you now have the resources to find those. Finally, as mentioned above, if you need specific help about fitting the calendar into your theme, reach out here with your url, and I will give a shot at helping you figure out the needed modifications.

Loushou

No problem. Also as a side note, if you do want to provide a link, you can actually send it to info@opentickets.com, and I can take a peak from there, assuming it is a public site. That way nobody else will get the link.

As for the language file, it is actually a pretty common feature in wordpress. Plugins are encouraged to have their own multi language translations, just like core wordpress. Here is another link that will explain what tool to get and how to setup your own language file. Hopefully that link will provide enough information to push you in the right direction.

Let me know if I can help any other way,
Loushou

Hey @juliepayne76,

Glad to head that 2/3’s of the problem is resolved. As for the remaining 1/3, I have some comments. You are correct that for Core WordPress you no longer need PO and MO files; however, for plugins, you still do need PO and MO files. This is because of the nature of how the translation system works. Every time there is a ‘string’ that needs translating (like the date format string), a mapped list is consulted by the software. This mapped list shows the software that the date format (or US english words), for instance ‘m-d-Y’ (US date format), should be translated to the UK equivalent ‘d-m-Y’ (UK date format).

For Core WordPress, when you select the Site Language and save those settings, what is actually happening is the software is reaching out to WordPress.org and asking for the proper PO and MO files. Those are then stored somewhere, and used later as that mapped list I talked about. With that in mind, the PO and MO files that you receive when following that procedure, is only for the ‘strings’ that WordPress knows needs to be translated (basically, any displayed words int he core WordPress software when you do not have any plugins installed).

In other words, once you change that setting, WordPress’s PO and MO files (the ones downloaded in the background) allow WordPress to know that the the word ‘Pages’ should be displayed as the word ‘Pagine’ when Italian is the language you selected. Conversely, WordPress has no idea that the word ‘Events’ should be displayed as ‘Eventi’, because Core WordPress does not know what an ‘Event’ is in the first place. This word ‘Events’ only comes into play once you install a plugin like OpenTickets.

Thankfully, Core WordPress allows any plugin kind of Piggyback this process. When you change that Site Language setting in the Settings page, plugins use that setting internally to determine which translation file they load for themselves. The plugin’s own translation PO and MO files are usually packaged with the software (our plugin currently works this way). Some plugins have employed a thirdparty service to distribute their PO and MO files (like WooCommerce) in a similar method to that of Core WordPress (the process you hinted towards in your message and that I described in detail above).

Basically, for most plugins, individual PO and MO files are a requirement. Many plugins already have a vast spectrum of different translations that they package with their software. Our translations are still in their infancy. As of today, we only have two complete translations, US English and German. We have partial Italian translations too. UK translations would be awesome to add to the collection, especially because of the date formats that you bring up. In order to do that though, we must follow the guidelines for plugins, which requires that each plugin provide it’s own translation for it’s own strings.

Hopefully this clears up why we have to have a UK translation and core wordpress does not require one,
Loushou

Hey @juliepayne76,

Thanks for doing that. Accordingly, I have responded on those threads to the questions in each.

Loushou