Digital experiences for all disciplines
Forum Replies Created
-
-
This reply has been marked as private.
see attached for screenshot
Update: so it’s trying to read a file that does not exist, i see that now 😉 so I duplicated the es.po file and renamed accordingly… will report back progress..
This reply has been marked as private.CSS? This is not just CSS, it’s: HTML/JS/CSS and PHP (presumably)
Maybe you do not understand the request?
I am asking you to modify your theme files, for a future release of your theme. I am NOT asking you to modify my site. And even if i was asking you to modify my site, CSS alone would not produce the result I am requesting (and suggesting is the best practice for “i agree” checkboxes)
You have to modify the theme file you provide us, and then provide that to us in a future version of the theme.
If all you want to do is satisfy this ONE request just for me, thanks, but i am suggesting you change it for ALL users of your theme.
Mohammad, i am not sure why you would ask for a URL. It’s not needed. There is an attached image, there is NOTHING to debug, only a slight design choice on where to put the HTML that displays the checkbox. I am saying it’s best to have the checkbox ABOVE the button. again, you don’t need a URL to understand and reply to this request. Just have a look at the image attached, and say “good idea, we’ll do that” or “sorry, we don’t agree”.
Mohammad, other theme authors have provided this functionality. So you can, if you want to add it via the theme. If you don’t want to, don’t. It’s just a feature request.
May 14, 2014 at 6:25 pm in reply to: 1.71: incorrect responsive css tweak breaks main nav menu for some desktop users #75089This reply has been marked as private.May 12, 2014 at 11:05 pm in reply to: 1.71: incorrect responsive css tweak breaks main nav menu for some desktop users #74346Ed – same result with the shared files.
Tried two different ways:
1) upload just the changes (responsive.css)
2) replaced the full theme with the latest.I use a child theme (in case that helps you isolate the issue)
May 12, 2014 at 11:04 pm in reply to: 1.71: incorrect responsive css tweak breaks main nav menu for some desktop users #74345Ed – same result with the shared files.
Tried two different ways:
1) upload just the changes (responsive.css)
2) replaced the full theme with the latest.I use a child theme (in case that helps you isolate the issue)
May 12, 2014 at 4:06 pm in reply to: 1.71: incorrect responsive css tweak breaks main nav menu for some desktop users #74242Ed, I allowed WP admin to upgrade the theme files to v 1.7.1 but I too had this issue with the menu. I have since replaced the responsive.css file with 1.7 version to fix the issue. But i now have theme files for 1.7.1 and a responsive.css file from 1.7
what do you suggest I do?
Should I return to responsive v 1.7.1 (and if so please provide instructions and link)? or leave it at v 1.7 for now?
Kyle. I don’t think that is the case here, and suggestion: be more explicit when you say clear cache: you mean browser cache?
So it sounds like you are saying we’re the only experiencing this issue, and as such it is/was an issue local to us (and you’re thinking browser cache).
So, it sounds like I have the hot fix update from the wp admin, but the responsive css from the v1.7 themeforrest files. That does not sound ideal. please provide a link to the v1.7.1 responsive.css file or suggest another way forward (unless the responsive.css file was not updated in v.1.7.1, because if that is the case I am good).
thanks
– Kyle
After seeing what you said in the other thread about the responsive.css file, all i did was go in and grab an older version of the file and it fixed the problem for me.
I too allowed the WP admin to upgrade the theme from 1.7 to 1.7.1. Theme forest says the latest is 1.7. Please let us know:
1) what the latest version is
2) if we should ever allow WP admin to update our theme files
3) if simply pulling in an older responsive.css file is sufficient here, (v1.7) or should I upload (replace) all of the theme files from the 1.7 v just downloaded from themeforrest.– chris
Oh I see what is going on, the client must have pasted text from their word pressor (or another site) into the product short description.
The text in the WYSIWYG is simple:
Cajita de 5 unidades(spanish)HOWEVER, looking at the HTML:
<span class="Apple-style-span" style="color: #444444;">Cajita de 5 unidades</span>.. so, because what they pasted had a span, was why we were seeing the issue.
span is not block level.
The solution is simple, i will tell them to clear formatting or to type their short desc into that box.
-