Digital experiences for all disciplines
Forum Replies Created
-
Posted in: We hit Power Elite.
-
I, too, would like to hear from Ed about this.
Currently any Swift Page Builder>Recent Posts block with 4 columns serves a 720×720 or 720×540 image scaled down to 235×235, creating a lot of unnecessary overhead and slowing site load times considerably.
I understand the logistics of making this work properly aren’t easy, but something really should be done about it.
January 16, 2017 at 5:52 pm in reply to: Several severe issues with Theme version 2.6.11 and Swift Framework 2.5.17 #310319If I had a way to replicate, I would have provided it already.
I know, for a fact, that Autoplay is enabled ‘by default’ for older posts – ones that were created prior to the feature being added. How do I know? We have 1500+ posts going back 4 years and it’s always been old posts that suddenly have autoplay problems, which occur after a theme or Swift Framework update, and no one has touched the posts.
I guess the best chance to reproduce is start out with Flexform, make some old posts, then update to a version of Cardinal that did NOT have the Autoplay feature, maybe make a few more posts (with videos, obviously), update to a newer version of Cardinal *with* the Autoplay feature and see what happens. No guarantee, but that’s about as close as I can get.
January 14, 2017 at 12:42 am in reply to: Several severe issues with Theme version 2.6.11 and Swift Framework 2.5.17 #310160Hi David –
We’re on Swift Framework version 2.5.23 and theme version 2.6.11.
Yes, the code is in the child theme functions file.
From what I can tell, either there’s been a change to the function or the js that appends those parameters. I may be wrong as I didn’t have much time to dig very deep, but I’ve used 3 different functions to disable autoplay for this theme since autoplay was added – I’m over trying to keep this thing working properly.
Here are the 3 functions I’ve used, all in my functions.php file in the child theme folder:
add_filter('sf_youtube_embed_params','sf_youtube_param'); function sf_youtube_param($param){ $param = '?showinfo=0&controls=1&modestbranding=1&rel=0&autoplay=0'; return $param; } add_filter('sf_youtube_embed_src_params', 'sf_youtube_param_new'); function sf_youtube_param_new($param){ $param = '?showinfo=0&controls=1&modestbranding=1&rel=0&autoplay=0'; return $param; } function custom_spb_functions() { function custom_spb_youtube_embed_params() { return '?showinfo=0&controls=1&modestbranding=1&rel=0&autoplay=0'; } add_filter('spb_youtube_embed_params', 'custom_spb_youtube_embed_params'); } add_action('init', 'custom_spb_functions');
For now I’ve written a quick js snippet to override any embedded YT parameters.
January 12, 2017 at 1:47 am in reply to: Several severe issues with Theme version 2.6.11 and Swift Framework 2.5.17 #309811The Autoplay problem is back after the latest updates and the code you provided no longer works.
Can I get updated code to fix this issue again?
At what date/version was the autoplay parameter added to SPB video block? From what we can see all posts with video elements that were created and published before the feature (autoplay) was added all default to autoplay on.
December 28, 2016 at 9:48 pm in reply to: Swift Framework history in database? spb_history_xxxxx #308280What’s the purpose of these if the pages/posts themselves already store revisions?
October 21, 2016 at 3:22 am in reply to: Several severe issues with Theme version 2.6.11 and Swift Framework 2.5.17 #297884Hi Ed –
I have not updated to the 2.5.18 Framework because I need to know, for sure, that the issues we’re having have been addressed and that no further fallout will occur. These updates are tested on a development server before being rolled out and time=money, so no time will be spent on this until we know it’s going to be worth it. Given that we are, again, being put in a position to do deep testing to verify all is well, any updates are an even more significant time commitment for my team. Given the number of people reporting issues, it seems to me that YOU need to do more testing before rolling out updates and not relying on customers to find these bugs for you.
1. There’s no effin’ way we’re going through 1500+ posts to check if the Youtube video has autoplay enabled. PRIOR to this update, none of the videos autoplayed. AFTER the update, they did. I have worked around this by editing the Swift Framework plugin code to set autoplay to 0. What changed that made them suddenly autoplay? Was the autoplay option something new? And, if so, does it default to ‘yes’? IF it’s not new, what changed that flipped all videos to autoplay?
2. I figured out a database manipulation to fix this.
3a. I’ve attached a screenshot that shows the parallax image issue as well as the code that controls it. I have a CSS rule to override the issue causing the problem (the ‘transform’ property). That screenshot outlines the rule and the location in the DOM that it applies to. If you disable my rule, you’ll see the issue. It’s currently a tiny bit of grey above the parallax image at the top, but it changes – sometimes it’s a lot more, sometimes less. URL:http://www.avidblogs.com/get-started-fast-with-avid-media-composer-software/
3b. This is ‘fixed’ in that we had someone edit all the pages/posts that had the problem.
4. It is spacing between rows/elements. I have attached a second screenshot with a reference for the element and CSS rule that I created to mostly get around the problem. If you disable my rule (.spb_content_element.col-sm-6.spb_text_column) you’ll see what I mean. All the content becomes very squished. This was definitely NOT the way it looked previously and the ONLY thing that was done after the update was:
- Edit the post and switch it to the Swift Page Builder to get around the ‘too narrow’ (width) issue. <– If we didn’t do this, the posts would look like the ‘too narrow’ screenshot attached.
- Edit the post to correct some text – after saving, THEN we lose the spacing between elements.
I’m angry and frustrated that we have had to spend so much time dealing with the fallout from these updates. We put our trust in you as the theme developer and we’re incredibly let down. We’re apparently not the only ones that feel this way. I hope I don’t have to reiterate that not all of your customers are running personal blogs where a few issues aren’t a big deal. That is definitely not the case with us and we rely on updates being solid.
Attachments:
You must be logged in to view attached files.October 20, 2016 at 8:47 pm in reply to: Several severe issues with Theme version 2.6.11 and Swift Framework 2.5.17 #297842I’m looking at the changelog notes and don’t see anything in this update that addresses:
1. The Youtube Autoplay problem (where it now autoplays all Youtube videos)
2. The space above Parallax images. The update says something about a fix for their backgrounds, but that’s it.
3. The column padding issue – columns now have 15px of padding added that wasn’t there before.
4. Referring to #5 in the list from my initial post – editing and saving a post after switching it to the SPB all text elements lose their spacing. This does not seem to be addressed in this update.Please correct me if I’m wrong.
October 20, 2016 at 8:28 pm in reply to: Several severe issues with Theme version 2.6.11 and Swift Framework 2.5.17 #297832I’m sorry, but this is not a ‘give it a try’ situation. This site is mission critical, not a playground.
Which issues did this update address, exactly?
I’m having the same feeling as OTTONYC – however, I *am* on the latest versions of the theme and Swift Framework.
I’m replying so I can get notified of updates to this thread and to alert OTTONYC that they are likely to still have problems after the update.
We’re also having serious issues, which I will detail in their own thread. I want to reply and get notified of updates to this thread.
I’m having the same problem after the latest update (2.6.1.1), amongst a host of other issues.
The site this theme is used on is huge and has over 1500 posts in addition to posts on 6 other languages.
Asking someone to go change the background color of the element to ‘fix’ this is, frankly, ridiculous.
There are so many issues, I’m wondering if you’ve even tested it at all. Yes, I’m angry – this is the 2nd or 3rd time there have been disastrous results after an update.
Hopefully you can get this issue and all the others I’ll be posting in related threads fixed soon. Right now I have to roll back to a previous version of the theme and Swift Framework and hope I can find a way to preserve new posts that were made since the update.
Is there any chance of this being added to a future update?
No, it didn’t. Love the theme, but customizing certain things is very difficult due to the file structure – something I’ve mentioned to Swift before. It’s arranged that way for their convenience, which I can understand to a degree, but it makes it nearly impossible to make customizations.
There *are* ways to possibly do this, but every time you update the theme you would have to re-edit the files again.
Sorry I don’t have better news.
How can I say this nicely – please re-read what I wrote originally.
I’ll summarize: We can’t preview galleries when the gallery is in Draft mode.
The one you viewed is already published because, hey, it took some time to get you into the site. We had to publish the one I was originally referring to, but the same issue is still present.
Create a gallery, then hit preview. Result: no photos are visible. Save it as a Draft, then hit preview – again, no photos.
If you publish it, you can then see the photos.
So, we’re wondering what’s going on with previewing photos for galleries that are not published.
You help is appreciated.
This reply has been marked as private. -
Posted in: We hit Power Elite.