Forum Replies Created
-
Posts
-
Hi Devin,
Yes I removed the slider and went with a plain grid which doesn’t have the same problem. But thank you for checking.
Frank
Hey Josue,
I agree on point one. But it wasn’t my intention to get into an SEO pissing match.
More to my point… Do you think SEO is even necessary these days? I mean a typical WP post shows up on Google and Bing within 36 hours (and usually sooner). Isn’t that fast enough?
How much attention span disorder are we talking about here? What are we sacrificing in our “need for speed.” No names being mentioned, but a certain SEO plugin seems to be causing a lot of problems for a lot of people.
Thanks,
FrankAnd here I thought you Enfold guys were born again hard. You mean you guys get to have a life? ;-)
Just kidding. Yeah I guess that makes sense.But seriously, I don’t get it. Even when I put it in the inspector just like you have done, it still doesn’t work. I think I’ll just have to move on.
Frank
Hi Ismael,
I spoke too soon. The clipping of the slider images happens in Chrome whether the admin console is open or closed, and whether there is a caption on the image or not. If you go to the link I posted above and load the page in Chrome you’ll see what I’m referring to.
Thanks,
FrankHi Ismael,
I found that this only occurs when the admin console is open. So it’s inconvenient but low priority.
However, that said, another problem pops up when the admin sole is closed. Namely, the captions above the images in the slider don’t display. So that is probably a more important issue for most developers.
Thanks,
FrankDavid,
Thank you for taking the time to respond. But the site is very much under construction, and a I have found a temporary workaround. Namely, Chrome. BTW, it’s IE9. That seems to be the offender.
Best,
FrankCheck and see if there is an .htaccess file in that directory. If there is check Cpanel to see if the directory is password protected. Remove the password protection.
OK, it’s clear I’m not the only one running into this.
FYI: I tried saving a content element with another browser, Chrome, and sure enough, I could not replicate the problem. I don’t want to say this is the workaround. It’s needs a QA to look at it, but like I said, so far it appears to be working.
Hi leighgoodman7,
I saw your post and I too have been dealing with this exact same same issue. I was pulling my hair out over this. I tried everything known to man and nothing worked. And believe me I can get very creative.
Anyway I tried saving a content element with another browser, Chrome, and sure enough, I could not replicate the problem. I don’t want to say this is the workaround. It’s needs a QA to look at it, but like I said, so far it appears to be working.
best,
Frank
