[UPDATED v2.2.0] šŸ˜ƒ Sudsy Page router for SEO-friendly clean URLs! (by Tech-Tonic)

That would be awesome and if you could attach a link to the editor that would be even better! Iā€™ve just subscribed to your plugin as well :slight_smile:

Would really appreciate if youā€™d improve the documentation because Iā€™ve literally followed all the steps but nothing is happening. ???

Hi @mukhtar007. PM sent.

Hi guys,

I would just like to say that @sudsy has been excellent (communication wise) and with additional, relevant and appropriate information provided by him, I have successfully implemented this plugin in my application. The plugin is now an integral part of my appā€™s dashboard and I no longer have to deal with userā€™s clicking the back/forward navigation causing the whole page to reload.

2 Likes

Just a quick note that Iā€™ve added compatibility information to the description. Basically, this plugin works with all modern browsers. It does NOT work with Internet Explorer.

Just wanted to follow up on this to report that I can now say with confidence, ā€œYes, indeed.ā€ See this forum post.

Hi, @sudsy

Is this plugin usable for html element??

I got my app ā€œreloadedā€ when I clicked on the link written in the html element.
It worked fine if I use link element.

Is there a way to avoid the reloading, or is this made only for the link element??

My app is a single page app, and I really need your plugin!!

Hi @rio, as you discovered, it works only with Bubbleā€™s Link element - not just any anchor tag on the page (such as one appearing in an HTML element).

If you have a unique problem or challenge, however, please post to the plugin help forum with the details, and Iā€™d be glad to see if I can help you come up with a solution or work-around.

Thereā€™s often more than one way to accomplish something in Bubble (as with most programming).

2 Likes

Finally, I got the solution for HTML element.
45

Thanks! Sudsy Page rocks!

3 Likes

onClick="history.pushState('','','https://yourapp.com/page/item')">

This is working for me thank you @Rio. I now hide the annoying link preview.

2 Likes

Hi @rio do you know how this code would look using toolbox run javascript.
We have a button here that is an image.

Hi @danielowega,

You mean to change the URL? Sorry, I donā€™t know how to do that with javascript.

Why donā€™t you just place a regular shape element on the image with the workflow and replace it by Link element later.
40

This is how it looks like with the link. Note that this link has a workflow since it is replaced from a ā€œshapeā€.
57

1 Like

Thanks yes I could do that but Iā€™m sure there is a way with javascript. @keith I think you are proficient in this, could you explain please?

@Rio I have solution! The code used before was correct but the url we tested with was causing an error and we never checked console.

VM622:2 Uncaught DOMException: Failed to execute 'pushState' on 'History': A history state object with URL 'https://yourapp.com/page/item' cannot be created in a document with origin 'https://storywall.app' and URL 'https://storywall.app/version-test/test'.
at HTMLButtonElement.eval (eval at <anonymous> (eval at b.create_code (https://dhtiece9044ep.cloudfront.net/package/run_js/290513b1c2ddb3f484b957c5c8fd24edd6d8c803e8b5e893061fdc3fc3d8c4c0/xfalse/x5:17:1063907)), <anonymous>:2:9)
at HTMLButtonElement.dispatch (https://dhtiece9044ep.cloudfront.net/package/run_js/290513b1c2ddb3f484b957c5c8fd24edd6d8c803e8b5e893061fdc3fc3d8c4c0/xfalse/x5:11:10315)
at HTMLButtonElement.q.handle (https://dhtiece9044ep.cloudfront.net/package/run_js/290513b1c2ddb3f484b957c5c8fd24edd6d8c803e8b5e893061fdc3fc3d8c4c0/xfalse/x5:11:8342)

Here it is:

2 Likes

Great! You gave me some insight here.

1 Like

@sudsy Iā€™m using this plugin, seems to work pretty well, thank you. :slightly_smiling_face:

Can you make the element resizable? Itā€™s pretty big and could get in the way.

Thanks for the feedback, @stone. Thatā€™s not an unreasonable request. FWIW, what I do (and would suggest considering in the interim) is simply ā€œSend to backā€ and stash it in a corner somewhere. Then, itā€™s not in the way and wonā€™t be easily clickable. As long as a portion of it remains visible between other elements on the page, it can easily be accessed when needed.

Thatā€™s what I do at the moment, just send to back. But due to itā€™s fixed width it could mess with responsive settings, say with collapsing groups.

I havenā€™t used this plugin, but for many others I place the element in a popup that is never shown, or a floating group beneath the page to avoid responsive issues.

1 Like

Every plugin element should be resizable and responsive by default. I donā€™t see a reason not to.

image