Forum Replies Created
-
AuthorPosts
-
Thanks so much for all your asisstance Rikard and team. We can close this ticket.
All the best.
Thanks so much for your quick reply and support. Further comments in private content.
April 18, 2020 at 4:06 pm in reply to: Slider error: Uncaught TypeError: ie.transitions._slideTimeline.stop is not a f #1204974OK thanks for finally investigating and proving a proper fix for the issue. I checked on my staging site, and it seems to work. I also enabled it on my live site and it works there too. So we can consider this resolved.
April 15, 2020 at 6:17 am in reply to: Slider error: Uncaught TypeError: ie.transitions._slideTimeline.stop is not a f #1203848Thank you. Please update me here.
April 8, 2020 at 8:49 am in reply to: Slider error: Uncaught TypeError: ie.transitions._slideTimeline.stop is not a f #1201820>> We are just suggesting a good or optimal web development practice. Would you install WP Fastest Cache and WP Rocket in the same site?
I realize what you are describing. But as I mentioned, I did not build the site, so both your theme slider and Slider Rev are already in-place on this page, and have been working without issue for years. For me to remove the theme slider, and re-create it using Slider Revolution, would require a fair amount of time on my end. That is time I shouldn’t need to spend–your theme and the plugin should work together without issue. If you want to spend your own time removing the theme slider and re-creating it with Slider Rev–on both my staging site and live site–that would be an acceptable solution.
>> I guess not, but if you insist on using the same type of plugin, you can start by eliminating the transitions, which seems to be where the issue resides as @yoqona pointed out above.
Again, you’re suggesting that we sweep the issue under the rug, rather than fix the issue. I would rather fix the issue.
>> Please contact the plugin author for additional help.
I will contact Slider Revolution. But what do we do if they say, “Ask Enfold support?”
>> We’ll forward the thread to our channel.
I don’t understand this comment–what does ‘channel’ mean? Does this mean you will forward this issue to your devs?
April 7, 2020 at 5:45 am in reply to: Slider error: Uncaught TypeError: ie.transitions._slideTimeline.stop is not a f #1201476Ismael, does Enfold theme have minimum requirements when it comes to the version of PHP that should be in-use?
April 6, 2020 at 6:48 am in reply to: Slider error: Uncaught TypeError: ie.transitions._slideTimeline.stop is not a f #1201145Your theme has an issue. Instead of fixing it, you’re asking me to spend my own time implementing a workaround. That’s not fair.
Let me be blunt. I want to use Slider Revolution and Layer Slider on the same page. I have done so for YEARS with no issue. Enfold’s version of Layer Slider is now incompatible with Slider Revolution. Are you going to fix that issue, or not? I’d appreciate a clear and direct answer to this question.
>> you should have created all your sliders with the revolution slider plugin in the first place
I didn’t build this site.
Have you passed this up to the devs? I think they would be interested to know about this issue.
April 4, 2020 at 4:54 am in reply to: Slider error: Uncaught TypeError: ie.transitions._slideTimeline.stop is not a f #1200730Hi Ismael,
Leaving Slider Revolution disabled is not a viable option in my case. My site has had a Slider Rev element on the page for many years now, and we are very happy with it. Trying to replicate the same element with Layer Slider will require a lot of time. It’s not really fair of you to suggest such a course of action.
Rather than sweeping this under the rug, the proper course of action is of course to diagnose the cause of the error and resolve it. I realize though that this will require some time spent by your team, and/or Slider Rev’s team. When incompatibilities between a theme and a plugin occur, how is it determine exactly *who* spends their time troubleshooting the issue? Regardless, are you able to pass this issue up to your devs to investigate?
>> Sorry about that. We actually forgot which plugins are deactivated prior and it’s a staging site, so we didn’t really thought of it. Is there a backup of or a restore point to a previous version of the site?
I’ll re-activate the plugins. But please be more careful with my site in the future :-(
Thanks.
April 2, 2020 at 4:47 am in reply to: Slider error: Uncaught TypeError: ie.transitions._slideTimeline.stop is not a f #1199942>> The slider is working properly when the plugins are disabled — the error is gone, so there’s definitely a conflict there somewhere.
I can confirm that the Layer Slider JavaScript console error occurs only when the Slider Revolution plugin is activated. So what is the next step towards resolving this issue? Are you saying the resolution is to leave Slider Revolution deactivated? Or that I should contact Slider Revolution to resolve the issue? Or will you elevate this incompatibility to your team to look into the issue?
>> We left the plugins disabled for now so that you can see the slider.
I see. But can you now re-activate the plugins that you deactivated? Please note that prior to this exercise, some plugins were already deactivated–did you note which? I’d like to continue to leave those plugins deactivated. In other words, please do not re-activate ALL plugins. Re-activate only those plugins that you deactivated.
Thanks.
March 30, 2020 at 6:50 am in reply to: Slider error: Uncaught TypeError: ie.transitions._slideTimeline.stop is not a f #1199005>> Can we access the dashboard?
Yes. The issue is present on both my live site, and my private staging site. So I will give you access to the staging site. I’ve shared those details in the private content area. In order to see the JS console error, you have to first click one of the layer slider navigation arrows (screenshot). Keep in-mind that any solution we implement on the staging site will later have to be implemented on the live site..
>> Have you tried to adjust the transition settings?
I don’t see how any configuration of the transition settings would cause a JavaScript console error. These same slider settings have been in-place for several years now, without issue. I hope I don’t have to change anything about the slider settings to fix the issue.
March 27, 2020 at 6:21 am in reply to: Slider error: Uncaught TypeError: ie.transitions._slideTimeline.stop is not a f #1198232Hello. Has anyone had a chance to look at this yet?
>> If you remove those line breaks in the debug mode and save the page, the breaks should be gone
OK thanks, that worked. I didn’t know if that field displayed in debug mode could be edited or not.
>> But the Shortcodes will be showing back to back not to easy to read.
Yes, that’s something I’ll have to live with I guess.
>> Also, I did not see the same text on the page and the extra breaks when I checked your page.
Yes sorry, the screenshot I posted may not have been from the same page I linked. The actual page is password protected. But the same general concepts were in-place, and same issues at at-hand. Sorry for the confusion.
We can consider this resolved.
>> you can enable the Advanced Layout Builder debug mode and you’ll see if the breaks are there.
I enabled debug mode, and in the new field it displays, I do indeed see blank lines in between page builder elements (screenshot: https://i.imgur.com/USuTaKn.jpg).
>> it can happen if you press enter in the text editor
Yes, that is indeed default WordPress behavior. But in this case, I’ve built a page using only the Avia page builder. At no point have I edited the page using the text editor. So if breaks appear in the text editor, wouldn’t it be the page builder that is adding them?
Thanks.
Yes we can close it. Thanks!
This reply has been marked as private.This reply has been marked as private.February 24, 2020 at 12:52 pm in reply to: How to export a single template, and import that single template on another site #1187303>> So the the answer to your question is no.
Thanks. I very much appreciate that clear and direct answer to my question. When you offered an alternative, without addressing my question, it was a little unclear whether what I wanted to do was actually possible or not. Directly answering my question makes that clear, easier to understand what you’re suggesting (and why), and in-turn easier to make progress on the issue at hand :-)
>> The easier and quicker option is what I explained above.
I appreciate very much the alternative option you provided. It actually wasn’t as viable in this particular case, so I went with Import/Export Layout Builder Templates (even thought it applies to all templates). But it’s good to know for the future.
We can consider this resolved.
February 24, 2020 at 8:03 am in reply to: How to export a single template, and import that single template on another site #1187221OK I see your suggestion, thanks. I’ll have a look at it.
Just to be clear though, I was asking if, via Enfold Child Theme options it was possible to export/import only a single template. Am I correct that the answer is ‘no?’
Great thanks–I see the edits. We can consider this resolved.
>> 2- Sure, we can do that :)
OK thanks. I’ve sent login info in the private content field.
OK I see that the Facebook icon is now displaying. I have two questions:
1. Do you have any idea why the icon was not displaying with the previous widget? As I understand, there should be no problems displaying a short code inside a text widget.
2. If I give you login information for my live site, can you repeat what you did there?
Thanks.
OK I have provided those. Let me know if there are issues.
You can see it in the footer here: https://feedxl.com/
>> If you like to speak directly to any one person you can mention that in the private content area for our admins to look at and if the person is available we will forward your request.
OK thanks for that. Sometimes my request is a little above what first level support can handle, so I’d prefer to go directly to a dev if possible. What’s frustrating is when a non-dev tries to answer my question, and does so incorrectly or insufficiently. It wastes his time and mine when that occurs.
>> We are a global team and we all work at different times and if the person is on leave then your request time may be longer so we try to help you.
Understood, and that’s OK.
>> To get your issue resolved fast please make sure it is within our support scope. Most of the time we try to help all our customers even if their issue is out of our support scope and sometimes this takes more time as well.
Yes, I understand, and will strive to do so.
>> However, if it’s really important for you to get this done, you can always hire a freelancer to do the job for you :)
My company has indeed hired a freelancer to do these jobs. *I’m* that freelancer :-) In a previous ticket, I was given specific code by Enfold support to achieve something, but it did not work as promised. So in this ticket I returned to ask why. Gunter was finally able to clearly answer my question.
Thanks again for the help.
OK thanks for that. In light of all this new information, I’ll go with a CSS-only workaround.
In the future, when I open a ticket here, is there any way to immediately speak with a developer? No offense to the people that respond, but often times they don’t understand my question, or don’t know how to resolve it. It then takes several days or weeks before an actual developer can reply to the thread.
It would save a lot of time if I could immediately speak with that person.Hi Basilis,
It would help me greatly if you could answer the question I asked in my previous message. To reiterate, would you expect that PHP code to set $time_format to false on all pages, set $time_format to false on just on the page with post ID = 517, or something else?
If you need to pass this question up to a developer, that would be fine.
Thanks.
December 10, 2019 at 6:05 am in reply to: Page builder's min-height seems to be causing problems #1164321OK cheers for all that. We can consider this resolved.
Thanks for the reply. I’m a developer, and comfortable adding custom PHP code to my site.
>> Unfortunately, it would require quite some time and customization of the theme to achieve this,
I’m not sure what you are referencing here. For clarity, let me perhaps re-phrase my question, with simplified code. I have added the following custom PHP function to my site and attached it to Enfold’s
avia_widget_time
hook:function change_avia_date_format( $date, $time_format ) { if ( 517 === get_queried_object()->ID ) { $time_format = false; } return $time_format; } add_filter( 'avia_widget_time', 'change_avia_date_format', 10, 2 );
Will this function set
$time_format
tofalse
on all pages, or just on the page with post ID = 517?Thanks.
- This reply was modified 5 years ago by FeedXL2019.
December 7, 2019 at 12:20 pm in reply to: Page builder's min-height seems to be causing problems #1163563Hi Gunter,
Actually I figured out the cause of the issue on my local site. On my staging site, I renamed the old PHP file to
slideshow_revolution.php-bak
. As a result, only the NEW PHP file (slideshow_revolution.php
) was executed. But on my local site, I renamed the old PHP file toslideshow_revolution-old.php
. As a result, both the old PHP file and the new PHP file were executed. Once I renamed the file toslideshow_revolution.php-bak
, the issue went away, i.e. the min-height was no longer applied to the element.I’ve actually experienced Enfold behavior like this in the past, in another ticket, i.e. simply renaming the PHP file was not enough–I had to give it an extension different from
PHP
. This behavior is a bit different to all other sites I’ve managed. Can you explain why this behavior is occurring? Is it expected, and/or beneficial in some way?Thanks.
December 5, 2019 at 11:38 am in reply to: Page builder's min-height seems to be causing problems #1162894Hi Gunter,
I have an update. First of all, I have three separate sites:
- a local site
- an online staging site
- an online live site
So far, I have been working on my local site. On my local site, when I replace the file (slideshow_revolution.php) with your updated file, there is no change–the min-height is still present. But when I do the same on the online staging site, it *does* resolve the issue, i.e. the min-height is removed on the element, as expected and as desired. That’s great, but can you help me figure out why the issue is still present on my local site? I realize it is difficult for you to troubleshoot, but let me describe what troubleshooting I’ve done so far.
On my local site, at the top of slideshow_revolution.php (your new revised version), I have added two error log print statements: one before if ( ! class_exists( ‘avia_sc_revolutionslider’ ) && function_exists( ‘rev_slider_shortcode’ ) ) and one after (screenshot). When I load the page in-question, only the first statement is printed to the error log. So apparently the class
avia_sc_revolutionslider
already exists, or the functionrev_slider_shortcode
does not exist. I did some more testing, and this evaluates totrue
: class_exists( ‘avia_sc_revolutionslider’ ), which seems to be causing the issue. That needs to evaluate tofalse
, correct? If not, none of the subsequent code is executed. But I’m still not sure why my local site and my staging site are discrepant in this manner…>> Yes please – and let me also have access to the php code so I can check it (and edit it) – and a link to the page please.
I of course cannot share with you access to my local site. But would you still like access to my staging site?
>> Is the slider created with an older version of rev slider? If yes this could be a reason why min-height is still present.
>> Try to save the slider again.Yes, the slider was created using an older version of Rev Slider. I’m not sure on the exact version number. But I tried re-saving the slider, but with no change in results.
>> You also can try to replace in file enfold\config-templatebuilder\avia-shortcodes\slideshow_revolution.php line 141:
Do you think it would be worthwhile to carry this out on my local site, given the symptoms I’ve described?
>> Clear all server cache and browser cache.
Yes indeed, I’have been doing that along the way.
Thanks.
-
AuthorPosts