Not sure if you are interested but i have been communicating with SP ref this issue and they confirm that the lasted version of Auto Clear fix is not compatible with FWP6.
they also make it clear from their response that they are actively discouraging the continued use of Backdraft as it will be difficult to manage the use of certain actions within your Applications Support folder.
Maybe it is time to go back to separate Application Support folders.
For me the development of Backdraft made life a lot easier, and progress was not so challenging and frustrating. although through the use of BackDraft i have learnt a lot, which i do not believe i would have done depending on SP support alone.
SP’s approach to the lack of collaboration with Backdraft is extremely disappointing and unnecessary the two products together compliment each other and make users like me more inclined to continue to use the SP product, and in so learn more as i progress.
SP i think you need to rethink your strategy on this one.
Just to be clear – we’re not actively discouraging the use of backdraft and if that was the message you received, please disregard it. What is the case is that Backdraft in outs current form is not compatible with the new responsive features in Freeway. This is something that we’re addressing together with Caleb and hope to have a solution very soon. You can continue to use Freeway 7 in the same way as 6 (i.e. not using the responsive features) along with Backdraft and the updated Auto Clearfix Action quite happily.
Not sure if you are interested but i have been communicating with SP ref this issue and they confirm that the lasted version of Auto Clear fix is not compatible with FWP6.
they also make it clear from their response that they are actively discouraging the continued use of Backdraft as it will be difficult to manage the use of certain actions within your Applications Support folder.
Maybe it is time to go back to separate Application Support folders.
For me the development of Backdraft made life a lot easier, and progress was not so challenging and frustrating. although through the use of BackDraft i have learnt a lot, which i do not believe i would have done depending on SP support alone.
SP’s approach to the lack of collaboration with Backdraft is extremely disappointing and unnecessary the two products together compliment each other and make users like me more inclined to continue to use the SP product, and in so learn more as i progress.
SP i think you need to rethink your strategy on this one.
Thank you for the clarification in respect of Backdraft that is good news.
However, and i do not want to belabour this point. I am somewhat concerned, even with my limited but improving knowledge and experience, that SP introduced FP7 without any reference to the issues associated with Auto Clear Fix, ie if you updated the action it would not work on FP6. I have read most if not all of your release docs and have purchased the latest reference manual, of course i have not read it all but focused on the inline construction elements. and have found no reference to the issue.
Surely in the transition period were people have FP6 files and moving in an orderly fashion across to FP7 some effort would have been made by SP to make the Action backward compatible. Of course the more experienced users would probably have the skill to overcome any problems in this regard, but at my skill level I rely on SP guidance and assistance.
Thank you for the clarification in respect of Backdraft that is good news.
However, and i do not want to belabour this point. I am somewhat concerned, even with my limited but improving knowledge and experience, that SP introduced FP7 without any reference to the issues associated with Auto Clear Fix, ie if you updated the action it would not work on FP6. I have read most if not all of your release docs and have purchased the latest reference manual, of course i have not read it all but focused on the inline construction elements. and have found no reference to the issue.
Surely in the transition period were people have FP6 files and moving in an orderly fashion across to FP7 some effort would have been made by SP to make the Action backward compatible. Of course the more experienced users would probably have the skill to overcome any problems in this regard, but at my skill level I rely on SP guidance and assistance.
We are designers and not programmers. We want to spend our time crafting beautiful websites. We don’t need an explanation “why do we use it”, “what is it good for” and “how can it be fixed”. We need solutions!
So please guys:
If you’re standing with your car in a dead-end - do nothing - call manufacturer. If she doesn’t know what to do - tell them that you purchased a product for to drive and not to stop and make them clear, that they have to change their attitude.
Thanks for clarifying this Joe, I too discovered the problem which in turn led me here to this thread.
I have a question; is it at all possible to have both version of the ACF action installed and use one for 6 and one for 7?
I have sites built in each which use the action.
Cheers
Mark
On 2 Sep 2014, 10:29 am, Joe Billings wrote:
Just to be clear were not actively discouraging the use of backdraft and if that was the message you received, please disregard it. What is the case is that Backdraft in outs current form is not compatible with the new responsive features in Freeway. This is something that were addressing together with Caleb and hope to have a solution very soon. You can continue to use Freeway 7 in the same way as 6 (i.e. not using the responsive features) along with Backdraft and the updated Auto Clearfix Action quite happily.