May 24, 2015 at 9:07 pm #16149
Latest versions are:
The theme contain only 3.0 Bootstrap and 4.2 FA.
Also did I find many code mistakes in your styles.css
Tons of double ;; and such things.
Please run your theme through CSS validator before release… it is a nightmare XD
Also do I get errors when trying W3validating the HTML5…
Thanks!May 25, 2015 at 8:58 am #21321
Thanks for your suggestion we will try to include the latest version of the bootstrap and FontAwesome in the next update. and regarding the css code mistakes in the version 1.0.3 we have already worked on all that error and fixed it.
Thanks.May 25, 2015 at 10:19 am #21326
Is there a possibility to throw out the corrected css files to us – prerelease of update?
I already corrected lots of the code, however it is still giving me 267 css errors back xD
Such things as float: center; (doesn’t even exist in CSS3.. you can’t floatcenter things)
Do you already know when the update comes out?
Thanks for being friendly in your answer.. some developers get angry when people point out codeflaws…May 25, 2015 at 12:32 pm #21328
The update is already released please find in on the latest update and regarding some functionality CSS3 validation doesn’t make it valid but we still have to add it in code to make it work in different browser.
Such as float:center; which you mentioned, zoom, o-transition and there are many of the examples of CSS property which W3 don’t validate but we’ve add to make it work in different browser. Even if you try to validate the CSS of twenty thirteen theme from WordPress it won’t validate as theme should look good in different browsers.
I hope that is clear.
Thanks.May 25, 2015 at 1:04 pm #21329
Hm, the double ;; semicolons are still in the current release style.css .. I have 1.0.3 installed…
I am currently working on translating the theme strings to german.
While doing this I found a few missing text-domains in the theme code. For example the file searchform.php is lacking the flat_responsive textdomain for the String “Search …”
I added the text-domain and copied the file to my child theme. Think I will find more…May 25, 2015 at 1:30 pm #21330
That seems unusual, but i will gave another look to the validator and amend it as soon as possible. Thanks for your inputs, i have noted the things that you have mentioned and it will be fixed too soon. 🙂
Thanks.May 25, 2015 at 3:16 pm #21334
Please find german .po and .mo files attached to this post.
I also attached the corrected searchform.php and content-portfolio.php. It can be placed in child theme folder or theme folder.
Please unzip all file prior to usage 😉
If you prefer using a child theme, please add the following code to the functions.php in your child theme folder:
Then create a folder called languages in your child theme folder. Put de_DE.po and de_DE.mo inside fo that newly created languages folder in your child theme folder.
Translations are now shown in frontend and admin.
EDIT: One more question:
You did a good job on responsiveness and retina icons.. however.. the custom logo does not go hand in hand with this awareness. Is it possible to implement @2x retina logo option in the next release? Thanks 🙂
In the meantime I am using “WP Retina 2x”-Plugin to achieve this usage of retina images on hires devices.
EDIT: And another issue:
Searchform does not open in mobile view. There is no such thing as a “hover”-event. Therefore the user can not access the searchform on a mobile device with touchscreen only – like phone or ipad.
Please add “open on click” option to the search icon!
Attachments:You must be logged in to view attached files.May 26, 2015 at 2:08 pm #21338Aki ChristinaParticipant
Dear Saskia Lund,
thank you so much! That came just in the perfect time as I come to open all files to start translation on my own.
Thanks for sharing.
Aki ChristinaMay 26, 2015 at 11:55 pm #21339
You are welcome!
Please make sure to also place the attached php files in your child theme folder (if necessary overwrite exisitng ones). Without them, in the current official release, a few strings are not translatable, due to missing or wrong textdomains.
The attached php contain corrected code.May 28, 2015 at 7:44 pm #21342
Thanks for the concern, and for your infomation we are updating the theme within a week with the fixes.
Thanks again for your patience and letting us know.
ThanksJune 24, 2015 at 1:04 pm #21431
It’s been more than 4 weeks.
Any update in sight?
ThanksJune 25, 2015 at 12:19 pm #21444
We are in the update process and it will be updated next week. We will inform you when it will be updated.
ThanksJuly 5, 2015 at 2:17 pm #21466
“next week” ist over 🙁July 5, 2015 at 2:17 pm #21467
“next week” is over 🙁July 7, 2015 at 2:43 pm #21474
Sorry for not updating the theme in time, due to earthquake in previous month our schedule has been heavily affected, so the update will be released next week with addition of features and validation of the Html and Css.
Thanks for your patience.
- You must be logged in to reply to this topic.