Member Avatar for swebdizajn

Dear friends,

I started a project which now needs a way to implement the other site. In fact, you should also publish the same content on the site PHP website partner. What are the odds to bring and what should I use? I tried the function (include), but this is not the happiest solution. Iframe think it also does not meet certain requirements.

Do you have any suggestions?

Thanks

  • 2 Contributors
  • 6 Replies
  • 367 Views
  • 3 Hours Discussion Span
  • Latest Post Latest Post by swebdizajn

Dani AI

Generated

Brief summary: wants a reliable way for editors to publish the same articles onto a partner PHP site; pointed toward a service-based approach. A practical, low-risk solution is to keep the CMS as the single source of truth and expose a small, versioned syndication interface so the partner ingests structured content instead of embedding or scraping.

  • Content model: store a stable content ID, slug, published_at/updated_at, status, author, categories/tags, short summary, full body (sanitized HTML), featured image URL and licensing/attribution metadata.
  • Editor workflow: add a syndication flag in the editor; when an item is published, enqueue a background job to deliver (or notify) partner(s) and record delivery status.
  • Delivery patterns: choose push (provider notifies partner via a secured endpoint or webhook) or pull (partner polls a paged feed); implement idempotency tokens, retry with exponential backoff and delivery logging.
  • Partner contract: publish a simple, versioned field contract and provide a test sandbox so the partner can map fields and test transformations before going live.
  • Media and HTML: serve images from absolute CDN URLs, avoid inline scripts, and sanitize markup before syndication.

Operational and SEO cautions: require TLS and authenticated requests (API key/token plus payload signing or equivalent), apply rate limits and IP allowlisting, and keep delivery logs for troubleshooting. If full article text is republished, have the partner set a rel=canonical to the original or display an excerpt with attribution to prevent duplicate-content problems. Start with a minimal proof-of-concept between the two sites, document the field contract, and iterate — this follows ’s practical recommendation to keep the data model simple and focus on secure, reliable transport rather than buying a complex turnkey system.

Recommended Answers

All 6 Replies

Member Avatar for jkon

If you develop both sites then creating a secure web service could be the best solution. Even if you are not familiar with web services a simple json client – provider approach with a password for security could do the job. If you don’t control at all the site where the content must be extracted then you could use DOMDocument to parse the content of URL (loadHTMLFile) and then use what you want (of course in the later scenario you should have copyrights approval)

Member Avatar for swebdizajn

Since we create content that we should give the second site, the copyrights are in order. The only problem is the technical feasibility of the implementation of example (articles, news pieces, etc ...). So something on the principle of RSS publishing, but that does not lead to other sites but the content is specially written for this site. We are the owners of the texts and databases, they are only as our customers. I hope i gave confusing problem.

Member Avatar for jkon

As I mentioned the logical way is to do it with web services. You are the provider , they are the client , it is exactly why web services created. Of course you should consider the security (in all solutions) , but clients application password (with one more layer that is yours and only for that app), more over SSL would be great (if you already have knowledge on that). It is not so different from this approach to do the same but not passing XML but JSON instead, that is ok if you or the client aren’t familiar with web services.

Member Avatar for swebdizajn

Beginning to realize the importance of web services. Does this mean that a good solution would be to buy the finished Web service, provide the necessary connections and if there is such a system over which we suggest?

Member Avatar for jkon

You have the data , so share them with your client. Don’t buy anything, learn. All you want to do is pass data from provider to client. That’s why web services created, you as the provider will pass data (in XML format) to the client based on an agreement (wsdl). Then they can do what every they like with those data. The main key to your question is not web services but passing the data in a secure way. I told you , you can pass them with JSON with a request password and your own security layer. It is not hard … it is just data …. (and then they –the customer- can decide how to consume the service)

Member Avatar for swebdizajn

If i understand it: We need to create news in xml format, then sends them in JSON format to the site where it should be disclosed. I must find a way to implement them there with respect to the security that you specify. However, since my editors still have the same text written in his own panel, and by keeping the same should be immediately posted on the site ... to me a little confused, how will all this take place, i wonder why.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.