Forum Replies Created
I just noticed that I have the same issue on a site. Did you make any progress on this in your support ticket?
I've been using Genesis for well over 2 years now and this update is the first that breaks something this major. So no it is not habitual in their case.
I have many clients in paid maintenance so I'm more sensitive than many on this and this is a big reason I've stuck with Genesis and will continue to do so. It has been very stable for us so far aside from the 2.2.4 layouts breakage which will apparently be fixed very quickly.
But regardless of this update issue for Genesis 2.2.4, I really think autoupdates of everything is an absolutely terrible idea. It looks good on paper and I understand the security concerns, but auto-updating everything is asking for trouble, trouble that many users are not equiped to deal with. I find that autoupdate everything philosophy very naive...
In our case, it also simple is not possible to have everything autoupdate as, a lot of the times, updating requires also updating translations we maintain separately (the vast majority of our sites are bilingual). Also, larger plugins often break things. From template overrides needing to be updated to changes in functionality as well as bugs introduced with early new major versions (yes, looking at you Yoast...), so we've always used a prudent approach to updates and take the time to evaluate them. The past history of the component being updated is also an important factor.
I leave the WP core autoupdate on for minor versions, but if they ever forced autoupdate for all WP versions, I'd deactive it right away. I don't want anything else to autoupdate. I really do not need the headache.
I wouldn't want to be a new WordPress user nowadays. The community is really sending mixed messages. Between the (very good) advice to test every big change to sites on staging or local servers and this recent push to update everything right away, I'd be very confused. Few updates are truly that time sensitive and critical. For example, it's not like WP 4.3.1 is suddenly a huge security risk now that 4.4 has been out a week or so. Same for most plugin or theme updates unless the update is one adressing a newly discovered and serious security issue.
I much prefer to test first and see if any issue come up immediately following a major update of any WordPress site component. That's what our clients pay us for.
Responded on Twitter but the 140 chars limit is annoying for this.
As I said there, I know of but haven't used Multilingual Press. I believe I've tried it ages ago but can't remember why I didn't end up using it.
I do use Multisite Language Switcher on every multilingual site I build though. It makes the different sites work together much like WPML would but without the overhead... or the problems. Link the same page between sites, create a new page in another language site if it doesn't exist, etc. Very easy to use, lightweight and has very useful hooks.
I see that Multilingual Press has several features that MLS doesn't. MLS is a very focused little plugin. Does exactly what it's supposed to and no more. I like that. But I'll give MP another go soon for sure.
Don't hesitate to ask additional questions here or on Twitter 🙂
Did you use POEdit as that page you linked to instructed? It will name the .po and .mo files correctly on its own when you save. No need to rename them.
Also, you say "widget titles in the admin widget area are in english and I want them in french", do you mean the name of the widgets provided by WordPress (like Calendar, Custom Menu or Recent Comments) or the widget titles you enter yourself? For the latter, you'll need to renter the titles in French. Theme translation won't help with that as they are not related.
I'd love to know how to customize them in functions.php (are there docs on those filters somewhere?) but the default values are indeed taken from the translation files (.mo file if it exists), however they are translated. I usually use CodeStyling or more recently, POEdit but translating with either does work and the text show correctly in French in the front end.
Salut Claude! 🙂
You would find those strings to translate (and more) in Genesis. To do that you'll need an application like POEdit or a plugin. I know there's a Genesis translation plugin of some sort. I never tried it as, early in my using WordPress, I discovered the CodeStyling Localization plugin and I've used that ever since. The advantage is that you an translate any plugin or theme with it (as long as they are localized properly). You can find it here:
The following plugin would also enable you to change the post info, post meta and footer text directly using text and shortcodes:
Dynamik will absolutely work fine with WooCommerce. I'm starting work on my first WC site that will use Dynamik (I've used WooThemes themes for that before).
I'd say that for working with WooCommerce in any theme though, a little coding will get you a long way, especially if you want to modify the default WC layout although there are some plugins on the repo that will help customize some of the WC display beyond what CSS alone can do. Just started using this one for example: