Create a new plugin, and in the “Shared” tab of the plugin editor under the “HTML Heading” section, define a dynamic value (key) .
Assign a test app to the plugin and open the test app.
In the “Plugins” tab of the test app, enter a value for the “key”.
In the “Settings” tab of the plugin editor, click the “Synchronize with GitHub” button.
Clone the Bubble repo to your local machine.
Make a minor change to the plugin on your local machine - e.g. just change some text in the README.md file.
Push the changes to the Bubble repo.
Again, in the “Settings” tab of the plugin editor, click the “Synchronize with GitHub” button so that Bubble pulls across the changes that were made on your local machine (since the repo is now ahead of Bubble).
Now go back to the “Plugins” tab of the test app, refresh the page, and note that the value entered for the key is gone.
Personnally, I avoid using Shared Header.
When a plugin create a conflict with another, it can be very hard to debug. I suggest to always include the header only on element that need it instead.
When you install a plugin with shared header, even if the element is not on the page, the shared header will be loaded.
Thanks for the info, @Jici.
So are you saying the shared header is output on every page of an app that uses the plugin, regardless of whether the page contains any instances of the plugin’s elements?
If so, I didn’t realize that. (I guess I could easily check it myself.)
What if a plugin contains multiple elements, each of which requires the same script? If the same header content is added to each element, will it be output multiple times?
Yes. When a plugin use shared header, this will appear on every page and not just the one that contain the element.
For plugins that contain multiple elements (there’s not a lot). This is a good question that I don’t know the answer. All my plugin actually that have more than 1 element doesn’t use the same header.
Yeah, I just confirmed it myself. That almost seems like a bug to me. Why load an asset on a page when it’s not needed? Even for actions, which don’t necessarily have a visible component, it seems Bubble should be able to load any required assets only if the action is used within a workflow on the page.
At any rate, user-entered information shouldn’t disappear after a github sync, but thanks for the heads-up on this behavior.
Yes I totally agree!
This topic was automatically closed after 14 days. New replies are no longer allowed.