[Pro] Protaculous Action (update?)

Freeway
1

Hi,

I am on my way to updating to 6.1 and am going thru my actions to update first.
I have an action called Protaculous used on 3 pages. The version is .7

I found it has been updated since to version 0.7.3 from Aug 2012 and not compatible to version 6 for FW.

http://actionsforge.com/actions/view/18-protaculous

Any advice what to do with this?

thanks,

Barry

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

2

Protaculous 2 is the new “ready for 6” version of the original Protaculous Action. It does not include the Carousel Action any more, that has been split out into Carousel 2, also for 6. The interface is a little different, and the code is massively streamlined. It is also no longer a “bundle” Action, which should improve its behavior during upgrades.

To successfully migrate from Protaculous to Protaculous 2, you will need to follow these steps, in order, exactly.

  1. Get a text editor handy, like the free and powerful TextWrangler from http://barebones.com
  2. Move to each page that uses Protaculous in turn, note which library is selected, and then click on each of the Function Body buttons. If there is code in either of them, start a new text document in TW named the same as the page, write down the chosen library, and then note which Function Body button contains the code, and finally the code itself (copy and paste). Remove Protaculous from the page.
  3. Publish your document once. (You do not need to upload.)
  4. Using your text files as a crib, move to each page that needs Protaculous 2 and apply the Action to the page.
  5. If your library choice was set to prototype or prototype-packed, you do not need to set anything. This is the new default; Prototype is always included when the Action is applied to the page. If you had chosen scriptaculous or scriptaculous-packed, then you may usually get away with just enabling Scriptaculous, which only loads the effects.js library by default. If your application of the Action is more complex, maybe using the drag and drop or slider controls, then you will need to also enable the relevant libraries. If in doubt, enable all of them. You’ll use more bandwidth per page view, but you won’t have to worry about inter-library dependencies.
  6. If your code was in the top Function Body editor in Protaculous, use the DOM Loaded Observer button to add it in Protaculous 2. If your code was in the bottom Function Body editor in Protaculous, then you use the Window Load Observer button in Protaculous 2.

There is a new option to create external script files, which will place your JavaScript in the Resources folder and link to it, further reducing the size of the page head and (apocryphally) improving your SEO mojo.

Finally, there is an option to use jQuery along with Prototype, but the usual warnings still apply here – it’s still a Very Bad Idea that you should only use if you can’t engineer a better solution.

Walter

On Aug 28, 2013, at 11:55 AM, Barry Hoffman wrote:

Hi,

I am on my way to updating to 6.1 and am going thru my actions to update first.
I have an action called Protaculous used on 3 pages. The version is .7

I found it has been updated since to version 0.7.3 from Aug 2012 and not compatible to version 6 for FW.

http://actionsforge.com/actions/view/18-protaculous

Any advice what to do with this?

thanks,

Barry

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

3

i follow these tonight.

i am glad i migrated from carousel to carousel2 six months ago so 1 less thing to handle.

thanks!!!

barry

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

4

Walt,

I followed your directions exactly and all went so perfect and smooth. You have a true gift for not just helping (as you probably hear a lot) but for the ability to give such clearly written directions and it is like you are right there!!!
I am totally out of Protaculous and Prot2 is being used now.

I went thru every action in my entire website and updated a lot of them. Some just do not have updates to v6 and I’ll see what happens.

next… buy 6.1 and then find some directions on how to change the site from 5.5 to 6.1.

thanks so much!

Barry

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

5

Hi Walter,

I’ve been trying to use the protaculous 2 action to create a draggable div, but it isn’t working. It was with the protaculous 1 action. Do i need to add anything other then the code: new Draggable(‘draggable’);

Thanks,
Edwin

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

6

Did you enable the Scriptaculous Drag Drop library? This should just work. Protaculous took an all-or-nothing approach to Scriptaculous, while Protaculous 2 allows you to pick and choose the libraries for greater “weight” savings. Drag and drop behavior relies on Effects and Drag-Drop to work. Make sure both of those are checked in the Scriptaculous Libraries section of the Action interface.

Walter

On Apr 23, 2014, at 5:01 AM, Edwin Verhoef wrote:

Hi Walter,

I’ve been trying to use the protaculous 2 action to create a draggable div, but it isn’t working. It was with the protaculous 1 action. Do i need to add anything other then the code: new Draggable(‘draggable’);

Thanks,
Edwin

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

7

Hi Walter,

It’s WebYep that causes the problem. When I remove the WebYep startcode it is working just fine. The old protaculous did work in combination with WebYep. Is it still save to use?

Edwin

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

8

Max has a work-around in there somewhere. I believe there is a way to disable WY’s inclusion of Prototype and Scriptaculous on the page if you dig far enough through Max’s excellent documentation. As long as the libraries end up on the page, both systems should work just fine.

Walter

On Apr 23, 2014, at 8:52 AM, Edwin Verhoef wrote:

Hi Walter,

It’s WebYep that causes the problem. When I remove the WebYep startcode it is working just fine. The old protaculous did work in combination with WebYep. Is it still save to use?

Edwin

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

9

Ah of course. Didn’t think of that. Thanx!

Edwin

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options