I want to create a list, where a user can click on the a list name and each name will take them to a unique set of content. Like a real estate app where a user might have a list of addresses and when they click on one address they see details and photos of that address.
Thanks for your reply.
I think you’ve misunderstood my question. I know how to make a list as such… what I’m after is the ability to click on each name of the list to take me to it’s own individual content.
I used the real estate example earlier…
So I might have a list of addresses of property on sale that I can click on. When I click on the first address I will then be taken to a page with completely different pictures and text to if I click on the second address etc.
I need to be able to set that link from the list to individualized content.
Am I making sense? Sorry I just don’t know the jargon.
I’ve been through the tutorial but I can’t find exactly what I’m looking for.
Let me make it exactly clear:
My home page is a list eg. rent, buy, sold
I need to be able to click on one of those above eg. I click on rent and then a page displaying all the addresses that are for rent opens
I need to be able to click on one of those addresses where another page opens to show me details of that property plus photos.
If you’re talking about the “send data to pages” tutorial… its too basic for what I’m trying to do.
If you;re talking about a different tutorial… would you mind posting the link here? I just can’t seem to figure out which tutorial has taught me this already…
Because I need the “rent” addresses and “buy” addresses and “sold” address all to be their own list. Without making a seperate page for each manually (because I want the flexibility to add more options in the future eg. “rent, buy, sold, home & land package”) I can’t seem to figure out how to do it.
If you want all of that on a single page, you could Pass the data in the URL parameter as type=rent or type=buy, etc based on what is clicked. And on Page load, use that URL parameter to filter the information you present to the user.
Of-course, this requires that all your information is of the same data type so that you can filter it accordingly on the single page.
I still can’t seem to transfer data from one page to another. I’ve made a list and when I click on “Item A” on the list I want to go to another page where the data is linked to the item selected.
I know your video shows how to transfer data within the same page but I suspect the codes are different when it’s to another page?
Well, if you need that selection to be persistent across a page change, you need to send that information to the next page.
Bubble has a default built-in facility for this (do the “sending data to pages” tutorial again, please).
In short, it works as follows: You have two pages Page A and Page B. On Page A, the user selects some thing in which they are interested. On Page B, you display information about that thing. Page B knows what information to display because (in Bubble speak), you “send data to the page.”
The page object on Page B has a data type associated with it. Select the data type of the thing you want to display.
Now go to Page A. In a workflow action (wherever it’s appropriate), Navigate > Go To Page. You’ll see place to enter “data to send”. Put the selected item there.
I think that’s where I’m experiencing the confusion… in data type. My list is going from one item on a repeating group to opening a new page with another repeating group both containing photos and text. It’s a little confusing, photo, text, user etc. And I keep experiencing errors because they’re not all matching… ugh!
Your page type should be a thing, sich as “Listing.” The repeating group for images would have a data source of “current page Listing’s photos” (or whatever you named the photo field on the Listing).
If you shared the editor link to your app, I’m confident this would be cleared up for you in a handful of minutes.
A Thing is a custom data type in your database. A page’s data type can only be a Thing, it cannot be a primitive. (e.g., a page cannot be of “text” type). But you can put any damn stuff on your page that you want.
If you need to pass a primitive to a page, you do that with a URL parameter.
If you want to display data about some Thing, you need to make that Thing. WHAT IS IT EXACTLY THAT YOUR USER IS SELECTING ON PAGE A?
It sounds like your page is like:
Click a picture of a taco: [taco picture 1] [taco picture 2]
But the tacos do not represent anything. Don’t do this. There’s never a reason to do this.
Instead, the tacos should in fact objects of type Taco in your database. A Taco would have fields such as name (a text), image (an image), meat (a text), toppings list (a list of texts). Get it?
When I click taco picture 1, NOW AM SELECTING AN ACTUAL Taco. I can pass the Taco to the next page. I can put the Taco in a shopping cart. I can edit the Taco. See?
The “Taco” I describe here can be anything. For your app, I guess it’s some sort of real estate thing. Make that thing.
Hello. You can do this. You just need the fields in your data type. You will have data type “listing” the listing has:
Agent: user
Title: text
Address: geographic address
Description: text
Photos: list of images
Leads: list of users (maybe people who favorites, or inquired)
Listing date: date
Days on market: number
Price: numby
And any other fields you may need.
For your agent, just create a multifile uploader and use it to save the uploaded images to the photos field.
You can append the search constraints. So, in your repeating group may have “do a search for” and search for the type “listing”. One constraint may be “created by=current user” this only shows listings created by the current situation user. Once your search parameter is in place, you can then modify it.
When displaying data in your group, you could create an image element, and its data source would be “this cell’s list of photos: first item” which would display only the first item on the list.