Sunday braimstorming

[Jimmi08]

Hi,
I am trying to find the correct approach to this, and sometimes when I write it down, it hits me.

Actual situation:
The external site sends $_POST data to the URL address we specified. Because of actual and future changes on their end, and the need to send this $_POST to more than one address, I needed to put some layer between those 2 sites. For now, I have done this manually, using logging and a simple PHP script. It is still maintainable, but the source site causes more and more trouble. So it is planned to manage this by e107 later. All receiving sites use WordPress and the Houzez theme. https://houzez.co/

In our country, we don't use IDX at all.

Now. They have 2 accounts on that source site (so $_POST is still the same for both companies), they want to combine them and use them as the source of specialized websites (just copies of the first one with a slightly different look - banner, colors - but different data). F.e. for location, for property type. For me, this is a nightmare doing this in WP.

I already tested that I can load data with API and JWT from the Houzez site to e107 site. I am not sure what I am doing - as always - I just used documentation and it worked. So maybe I will just display data with e107 (not full property management). Or I can receive those $_POST separately on e107 site and save them in a simple table (it would solve the logging issue too). I have considered e107 multisite, but they are different domains, and I only tested multisite on subdomains or subdirectories. Not time for this now. But creating e107 copy is pretty easy.

What do you think? Am I going the right way when I want to use e107 for displaying data from another source (WP)?

Thanks

[rica-carv]

@Jimmi08 If i understand correctly, you want to send $_POST data from two sites to a single E107 instalation???
And in the procedure, change sites / url's???
Isn't that confusing to the front end user??
Why not convert both sites to e107?
Wouldn't it all be easy if you had everything under the same CMS / Engine?

[Jimmi08]

The first site is not under our control. It is a real estate portal that they need to pay to get their data with $_POST af least.

I don't have the next 10 years to develop a real estate solution compared to Houzez in e107. And I wouldn't do it either - with all those issues not solved for years. When I started with e107, I told developers that I was looking for real estate solution, all my testing, questions, issues were pointed that way, to that goal. So I could have WP alternative. Can you imagine that Houzez functionality with e107? Maps, variability, options... Time, time, time. Not paid time for sure. And I need to learn stuff like AI implementation for website - to help visitors with AI, AI SEO... There is already implementation of llms.txt for AI engines, and e107 is not able to solve SEF-URLs correctly. Yes, I am sure I would so skilled as Deltic, I would have this done long time ago. But I am the best in support, not in development.

By the way - I did site in e107 similar way, everything is perfect, speed, urls, look, importing... and do you know what? Now I need to change it back to Wordpress, do you know why? Because if I end, nobody will be able to continue. They cann't depend on one man (woman) - so now we are back to Wordpress solution because anybody can overtake it and continue (I don't think so, but let them their illusions). It was a decision above me.

Back to the topic.
You are looking at it as your site. No, they have f.e 5 domains, each for specific area of real estates. It is exactly opposite - users are confused if they have everything in one place, too much information... They did this for 20 years, so they know why they do this. I can create 5 copies in WP, I will hate it, they will not pay for support of each one (because they are copies, correct?... I can hear it already). The budget is limited. So maybe if I have one WP site (or e107) with all data and with API displayed desired content on single site... it could solve management issue. Because e107 is stable, safe, quick etc.

Wouldn't it all be easy if you had everything under the same CMS / Engine?
Yes and no. It is not the trend nowadays. You can use one system as backend and other on frontend. It is about API. Houzez team will release their API plugin exactly for this purpose.

[rica-carv]

@Jimmi08 I get your point, but relying on $_POST data between two different sites is aiming for trouble.....
Just my two cents....

[Alex-e107nl]

@Jimmi08 most of the time people think to much, you can sync data between databases, so all you need is a app where you put in all the relevant data for input and sync the table or fields with the databases to what ever you want, i do the same with user fields from WHMCS to e107 every 5 minutes with a cron.. The input is with whmcs but it is used on 3 e107 websites... and with a key so not all e107 sites get the same users.. And if you document your work right everyone with a little it brain can take over, man or woman :-) That's not a argument as long as you use open source software...

[rica-carv]

you can sync data between databases

Or better, have a common database with the common tables for all the sites...

[Jimmi08]

I did it. The look is an intention from the legacy version with bootstrap 5 update.

https://reality-trencin.sk/