Conflict with Backstretch and slider

I am using the backstretch block to create a different background on every page for a client, but when I activate the revolution slider, the backstretch image disappears once I leave the edit mode and publish the page.

I think there is a JQuery conflict of some kind, but I am unable to locate the problem.

Thanks. I have the backstretch block in all of the other pages on the site and it is only broken on the test page with the test revolution slider. It seems that the slider has initiated a conflict, not the other way around.

Maybe its just the slider. Is it still broken with the slider and no backstretch? I don't use either of the them so code wise I couldn't tell you although those symptoms do tend to be JavaScript related.

Thanks for your help with this. I am only seeing the errors on the /test page because that is the only place I have implemented the slider. When I remove the slider, the backstretch add-on functions properly and the page works as expected. It is only when the slider is placed on the page that the page is broken.

I am developing this page to replace the homepage athttp://europemissions.org. The only difference between the two pages is the content block that is removed and I have selected a right sidebar page. With that said, it was broken with the other page type as well.

I am confident the problem is related to the slider somehow overriding the settings for the background image. I have yet to hear from the developer of the slider at this point.

This problem arises because although Revolution slider is a very nice looking slider, it breaks the coding rules used by concrete5 by globally hijacking the jQuery $() magic function. Revolution slider is not available from the concrete5 marketplace (only from 3rd party marketplaces) and never will be unless the developer of revolution slider resolves this rogue behaviour.

The consequence of the hijacked $() is that any on-page javascript that relies on $() being defined in the global namespace will fail. The $=jQuery workaround will only work if the javascript it is applied to is all within closures, so it could cause a host of secondary errors. It needs to be placed within any javascript loaded by a theme or addon when the page is viewed where $() is used. In the above instance of this issue, the addon file affected by revolution slider was called function.js.

The only guaranteed fix for this problem is to get a refund for revolution slider and use a different slider, one from the c5 marketplace that behaves properly with respect to $().

EDIT:
The google search below will show all the issues posted relating to revolution slider.