PHP Not Available

PHP Not Available

vncj9i70o4vncj9i70o4 Posts: 2Questions: 0Answers: 0
edited October 2013 in Editor
I want to implement Editor in an environment where PHP is unavailable. I tried getting it to work without it already, but my skills are not good enough to even determine if it is possible to run it completely locally.

Here is the situation: I'm building an HTA, and I only have access to client-only technologies like Jquery, Bootstrap, and DataTables. My database will just be a JSON file. I though Editor would cover all the functionality I needed to edit the tables, until I saw that PHP was used in EVERY example.

Is it possible to run editor in a client-only mode? If so, how.

Replies

  • allanallan Posts: 63,498Questions: 1Answers: 10,470 Site admin
    There is an example of how to use Editor without any server backend at all here: https://editor.datatables.net/release/DataTables/extras/Editor/examples/localstorage.html . However, that's only useful for one person, since it uses localStorage (there is also an example I have using indexDb in the browser if that is of use to use, but again is local only).

    There are two other points:

    1. The Editor communication with the server is documented here: https://editor.datatables.net/server/ - allowing Editor to be implemented with any server environment that is desired. (for example Tactical Enterprises have developed a Java backend for Editor: http://jed-datatables.ca/jed/ ).

    2. If you want absolutely no server environment at all on your side, but you still want users to share information in the tables, then there needs to be a location the data can all be stored in - using a service such as Firebase is an option and could be directly integrated with Editor using its API.

    Allan
  • vncj9i70o4vncj9i70o4 Posts: 2Questions: 0Answers: 0
    We may be able to get a real back-end, but at this time, we are subject to what we have. We have to keep moving forward regardless in order to get attention. Regardless, the best we have is a shared drive to store the file on, which should be all we need for a while. The project that I, specifically, am working on only requires local storage, but it needs to be persistent outside the browser, because people will sit at different workstations.
This discussion has been closed.