Options for store plugins

[Godber (David Morris)]

and me

[dan (Dan C.)]

We’re looking into that, but in the meantime, here’s a direct download link to the project: https://dl.elementsapp.cloud/g/0VrNlHKsSZbM

And here’s some info on how to convert an Elements URL into a standard download link…

Converting an Elements App link to a direct download

To generate a direct download link from an Elements App link, append the unique identifier from the original link to the elementsapp.cloud URL.

Example:

• Elements App Link: elementsapp://downloadDocument/0VrNlHKsSZbM
• Direct Download Link: https://dl.elementsapp.cloud/g/0VrNlHKsSZbM

[handshaper (Robin Mair)]

Awesome, this works really well.

I did delete the code that was in the Javascript section of the component as you had moved that to the Template area. Was great seeing how the PORTAL option was used for the scripts.

Which brings up a question: when would the scripts be placed in the Javascript section of the component?

I tested moving the scripts into that section but it did not work.

[handshaper (Robin Mair)]

Playing with this custom component brings up a question. How do you setup a custom component to correctly handle TABBING from one field to another?

I noticed this when using the component that when I hit TAB nothing happens.

[dan (Dan C.)]

The tabbing issue is a bug/something we need to implement!

[handshaper (Robin Mair)]

Today when I tried to run the page with the store custom component I get this error instead of seeing the product Buy Now button.

This error seems to be happening to ALL custom components as another one of mine is showing the error. Plus I tried recreating the product component and it had the same error.

[tpbradley (Tom Bradley)]

@handshaper Can you confirm what version of Elements you’re using? We released an update yesterday that should fix this issue, Version b15 (22935).

Elements Beta 15 (build 22935)

Sometimes beta builds are like busses, you wait for ages, then suddenly several coming along at once! What’s New in Beta 15? Fixed an issue with Custom Components not appear in Preview Fixed an issue with the Component Inspector appearing empty Update to the latest Beta Elements should prompt you while it’s running to let you know there’s an update, if it doesn’t you can select the “Check for Updates…” menu option from the “Elements” app menu. Please note: Sometimes it takes a while for the …

If you’re still seeing this issue, would you be able to upload the document using Elements Cloud and send me the link?

Cheers

[handshaper (Robin Mair)]

I did get the b15 update and it does fix the problem.

The only problem I’m experiencing now with custom components is that I cannot delete them. I can delete them from the project but when I close and reopen the project they reappear. I have tried this a couple of times.

[tpbradley (Tom Bradley)]

Great! We’re aware of the deletion issue and have a fix ready for the next beta.

Cheers

[AngelArs]

Vibracart Pro makes a simple plugin for Rapidweaver classic.

Hopefully they will do the same for Elements.