Yay, I’m right! First time in a while. Feels good to be helping other members of the community.
I’ve just tried that solution, it works, but it’s quite slow, the user gets to land on a page for 1-2 seconds and only then is redirected to another page
True. I forgot to mention that we would need a new category of workflows that are not bound to pages and that are ran before any page is loaded.
I’ve always found that having all WFs(except API) linked to pages is quite limitating as we can’t build a proper access and routing model.
no yay. you lose access to the browser back button.
Correct on both counts. Revisiting it after the post and doing a bit more testing, I decided it was too hacky to want to put it up as an option. I didn’t really want to push new users to try it and then think Bubble was slow or bad or whatever, not understanding the implications of the method. Your reposting of my removed message is a bit of a breach of confidence, but whatever, I guess I should’ve had all those thoughts before pressing send and that’s on me.
If your database is not large, it works. It will work for pages like “support” and “login”. But I would no longer would recommend using it for user pages or any “thing” with more than a few entries. Apparently putting it on apps where the database has many “things” is also slowing it down? That’s by feel not testing (disclaimer). Allright I hope that answers the question “I don’t know why you withdrew your message”.
Also @danielowega you’re right, but UX-wise, I mean, pretty inconsequential. Who would navigate to a custom url from a page they want to go back to. CTRL+T then add URL is what most people do. Otherwise you got wherever you are from a link and DO OBVIF_(*OUSLY NOT use those urls for navigation from within the app… So back button is probably not an issue here, even if Bubble opts to do redirects that way.
Now @ Bubble. When I first opened this forum this was a discussion I was interested in. That was 2 years ago and I know you said it was difficult for your infrastructure to support such a change. Seems to be a pretty hot topic, and I’ve seen firsthand how you listen to your users. Looking forward to seeing this implemented.
We do not share sentiment but anyway its not what most users do, when thinking about ux you are aiming to be inclusive of everyone even that small percent.
oh, my apologies, didn’t realize that, shall i remove it? can do easily.
Another way to do this (but a bit nasty) is to host the “main” site elsewhere and frameset the bubble page including the name.
mypage > mybubblepage/index
The path should get preserved.
I don’t know I’ll defer to your better judgement and experience. We’re all on the learning journey and it’s just that I look at what I was doing back then and it was unoptimized, and slow, and just really bad compared to the way that I build now. Like I said, hacky and potentially slow, and you’ve confirmed it a few posts down. If you think it’s valuable knowledge to have on the forum leave it. Otherwise remove it I just wasn’t sure it was truly a good option.
I’ve been really struggling to find a way to make simplified links for my users to share their profiles on social media. I hope a solution is devised soon. Here is a recent post I’ve made about it, which also links to a previous thread where there were no desirable solutions presented for my use case:
let’s keep it so others would know about this alternative even through it’s hacky and slow
Not sure what the “workaround” was, but if it’s the 404 redirect method referenced in this thread, I’m pretty sure that’s been discussed before in the forum.
The problem, of course, is that regardless of what appears in the address bar, it generates a 404, which tells browsers and search engines that the requested resource doesn’t exist (which is precisely the opposite of what’s desired).
Anyway, I know of a couple ways to create a dynamic home page using only Bubble logic (workflows) on the index page itself, but neither uses the “Path”, so they are not ideal (but almost certainly better than generating 404’s). I’ll post them under “Tips” so as not to clutter this feature request thread.
can’t wait to learn that
You could probably build something workable with cloudflare forwarding rules and browser URL rewritting.
If you forward in Cloudflare
Then you just rewrite the URL in browser as http://domain.com/@levon replacing the history in browser.
@ char needs to be URL encoded(%40 I think)
Disclaimer: I haven’t tested this approach.
good idea, @JonL i thought about it, but when redirecting cloudflare won’t add @levon to the new URL.
I thought to use cloudns.com that can add the path to the destination URL, but they don’t allow A record and web forwarding for the same host (both would have to be for mydomain.com)
Bubble moaned when we tried to do this with Cloudflare.
I put together a demo page…
Thanks for this, @shot and it’s a great example, but it’s a bit different from what we need, we don’t want to use neither # nor ? in the URL
Understandable. I think a Bubble solution is going to be the ticket, which is why I hope your feature request gets implemented.
yeay, we have found an almost perfect solution and posted it here: Pretty URLs with Dynamic Links - mydomain.com/dynamiclink - Solution from Zeroqode