-
Posts
-
My site uses the portfolio section to showcase our projects. We use the grid display (See link) But it’s been acting weird.
If we click on one, we can use the forward arrow of the details area to move to 1 or 2 more items. But that’s it. We can’t page through them all. And the back arrow doesn’t work at all.
In some cases when we click on one, a different item detail opens or it is half the right item half the wrong item. Very weird.
And often, we will find a second Read More box floating over the content.
I updated the theme in the hopes this was a bug that has been resolved, but it is still happening.
Hey,
Please try de-activating all active plugins and check if that helps. If it does not, please create temporary admin logins and post them here privately so we can look into it :)
Best regards,
YigitI did deactivate all the plugins. It had no effect. I have created a login for you, see the private Content area.
Hi,
Thanks for the update. I see some jQuery errors on the page, but I’m not sure what is causing them. Does the same problem happen if you activate the parent theme?
Best regards,
RikardHmmm. That’s interesting. I can check.
To activate the parent theme, do I simply deactivate the child theme? Is there a “safe” way to do this so I don’t lose any child theme settings or custom CSS?
Hi,
Thanks for the update. You can simply select to activate the parent under Appearance in the WordPress menu, you would only need to have it active for a minute or two to check if the same problem happens when the parent is activate. You shouldn’t lose any settings, but I would recommend that you export the theme settings just in case something should go wrong.
Best regards,
RikardThanks Rikard,
I just tried it. Although the portfolio looked a little different, because of not having the child theme settings, it behaved in the same strange way. Not able to move to more than one item. Not able to go backwards (only the right arrow works). Two “read more” buttons floating over the content. Content from 2 items in the same page. Etc.
Now what?
I’ll add credentials for you in the Private Content area.
Hi,
Sorry for the late reply and thanks for the login, I see that your portfolio items with asterisks have base64 code in the editor under your big button shortcode. I was not able to decode this or see anything on your front end.
But when I added this to my localhost I got the same error in the console as above.
What is the code for? Perhaps removing it from all of your entries will solve the issue.Best regards,
MikeHmmm. I suspect a previous editor may have done a copy and paste without clicking on the Text Paste “T” first. I’ll have all the ones with asterisks remade and will report back on what happens.
Hi,
Thanks for the update, we’ll keep this thread open for you in case you should need any further help.
Best regards,
RikardWell I went through and removed all errant code from every portfolio item (not only the ones with asterisks.) The problem persists. Do you still see the same error messages?
Hi,
Thank you for checking, yes the error is still occurring. Is your server using object caching? Please check if you can clear your server cache if any. Since your site is live, please check your webhost to see if you have the one click staging site option, this is a option in most cPanels to create a staging clone of your site so we can test on it and your live site will stay up and running, untouched. You can always ask your webhost to help you with setting this up if you want.Here are some screenshots of what it would look like:
Otherwise, I would like to enable your parent theme and disable your plugins to test further.
Best regards,
MikeWe are using a Managed WordPress host – no C-panel.
If you look through the thread – you will see that disabling the plugins was the first thing we tried.
Hi,
Ok, I did see that you tried enabling the parent theme and disabling the plugins without success, but I was hoping that if I tried the same that I may see a clue in the browser console. Unfortunately, the only time I could reproduce your issue on my localhost was when I added the base64 code. So since you removed the code but the error is still occurring so I wonder if your server is using object caching which would still output the deleted code.
So if you can’t create a staging site to test with can I test on your live site perhaps Sunday before noon? When do you have the least traffic?Best regards,
MikeMike,
I understand better now, thanks for your reply. I think you see you have access to the site in credentials, right? We are keen to have this issue resolved since we have been working on it a long time. Please don’t wait until Sunday. We don’t get so much traffic that waiting until the right time is more important than making progress on this ticket.
Please proceed as soon as you can.
Hi,
Sorry for the late reply and thank you for your patience. I have found that adding a full-width button in the Ajax Portfolio Preview text field causes theFailed to execute 'getComputedStyle'error. I have reported this to the dev team.
I suggest changing your full-width buttons to X-Large buttons in the Ajax Portfolio Preview text section as a temporary solution.
Since your buttons are added as shortcode you can change the buttons by simply removing_bigfromav_button_big
Hopefully, this will save you from recreating every button.
I will post an update when the dev team returns a patch for this issue.Best regards,
MikeMike,
Thank you for looking into this and for your suggestion with screenshots. Unfortunately, removing the word “big” had no effect. It didn’t make it extra large it just made it a normal looking button. (which is fine actually).
The buttons don’t look any different in live view. Which is weird. I even looked in Firefox and using Chrome’s Incognito.
You may have found a problem. But you didn’t find the solution to THIS problem. I’m starting to think we should scrap using a portfolio altogether or switch to another theme.
Hi,
The dev team has returned a fix for the full-width button in the Ajax Portfolio Preview text section: “The full-width element full-width button shortcode broke the layout because called outside shortcode tree and creating an extra section.” Full-width elements try to full-width for the screen not just the element, so typically placing a full-width element inside a page element will cause an issue. In this case, the dev team edited the full-width button and the portfolio element so this will work correctly.
This will be included in the next release. In the zip file in the Private Content area, you will find two files:
buttons_fullwidth.php & portfolio.php
via ftp, please save a fallback copy of your current files and replace these at these locations:
\wp-content\themes\enfold\config-templatebuilder\avia-shortcodes\buttons_fullwidth\buttons_fullwidth.php
\wp-content\themes\enfold\config-templatebuilder\avia-shortcodes\portfolio\portfolio.php
Then clear your browser cache and any cache plugin, and check.Best regards,
MikeThanks Mike for your continued support and clear instructions. We are on managed WP hosting, so I’ll have to send it through the hosting team. But I’ll do it today and let you know the results.
Hi,
Glad to hear, and thank you for your patience while we sorted this out. Unless there is anything else we can assist with on this issue, shall we close this then?Best regards,
Mike
- The topic ‘Portfolio Grid display not working right’ is closed to new replies.