Hi,
The Slider Revolution bundled in the most recent available copy we have via theme forest is 6.7.10. We used a link on the forum provided by TagDiv to update our plugin to 6.7.12 last time. Will a new link be provided or will we have to wait until the next theme update? We are a bit concerned as WordFence has indicated there is a security vulnerability in 6.7.12.
We do not need a copy of WPBakery.
Thanks for your time.
Update: We have narrowed the issue to Flex Block 1. The issue continued to occur when we rolled the theme back. Flex Block 5 is working before and after the update. We have not tested whether 2-4 is working or not. We will use Flex Block 5 in the mean time. We have no idea why Flex Block 1 is misbehaving.
Hi Bettina,
We have tested the YouTube embeds using the code to bypass our cache completely. We are still having the issue. We have noticed it does not matter if you access the article with or without the cache enabled. The first visit will always be the default embed size and the second will be the correct full size. Do you have any other ideas what may be the cause?
Hi Bettina,
I have followed the guide earlier, and it makes the problem worse. I think it is better to use an image to show the issue we’re trying to solve.
https://i.imgur.com/oF5s9z1.png
We are trying to get it to maintain a 16:9 aspect ratio at all times. If left at default, it will display something very close to 16:9, but not quite. As you can see from the image, if we set a video to a specific height, the video will stay at that height regardless of how the theme scales for different widths. What we would love to do is to have a setting that locks the width:height to the 16:9 ratio at all times instead of the slight off ratio that the default mode currently uses. If that is not possible right now, we hope TagDiv will consider adding this setting in the future.
And we will investigate the article embedded and caching issue and get back to you. Thanks for pointing us in a direction for this matter.
Hi Calin,
I double checked using your instructions. I was editing the correct post ID. I tried another post just in case, but the result was the same. I checked the article using incognito mode: no success. Changing the score in WordPress’ editor successfully changes the td_review_key value in the database, but not the other way around. You can see the result here: https://imgur.com/a/4fM3FNs
I are running into a very strange issue with td_review_key in my test environment on Local using mySQL. Saving a review score in WordPress will correctly update meta_value for td_review_key. However, if I update the score using the td_review_key’s meta_value, nothing happens. When I checked the database queries using Query Monitor, I noticed the post with the review is not querying the td_review_key meta_value at all.
You can see the updated value in this image, but no change in WordPress in this screenshot.
I have cleared the browser cache multiple times, used a new browser, and incognito mode to confirm updating database scores are not being reflected on the posts.
Please let me know how I should proceed
I have been doing final work on the theme before deployment and have realized that I think the tdc_review might be for User Reviews as website reviews appear to only be set as regular articles with a review score attached to the article.
I am not trying to convert our existing reviews into user reviews. I am trying to turn our existing reviews into the type our writers would use the “add new post” function and then add the score to the post. I also need to copy over our old score into that post’s score.
If I do not want to convert these reviews into user reviews, but rather regular reviews posts, do I still use the tdc_review post type or do I change all the old reviews into posts and proceed to copy old score to td_review_key?
Hi,
This partially covers what I need as we will be able to convert the reviews into the Newspaper format with this. I can’t seem to find where the score is being saved in the screenshots as we will need to convert the scoring from our current theme to Newspaper.
Thanks.