C0Rrupt
Beginning Developers
This space is for newcomers, who wish to build a new plugin or to customize an existing one to their liking
Elgg Technical Support
Get support from other Elgg users
Plugin Development
Talking about how to write plugins
C0Rrupt replied on the discussion topic Implementing elgg_file_viewer extension- C0Rrupt replied on the discussion topic Implementing elgg_file_viewer extension
- C0Rrupt replied on the discussion topic Implementing elgg_file_viewer extension
- C0Rrupt replied on the discussion topic Implementing elgg_file_viewer extension
- C0Rrupt added a new discussion topic Implementing elgg_file_viewer extension in the group Beginning Developers
Do you use the File Viewer plugin at https://elgg.org/plugins/2648090? It should work on Elgg 2.3. It supports a number of file types already. For other file types I think you need to provide a view in views/default/file/specialcontent where the exact location within depends on the mimetype of the file. The view would deal with displaying the file. For some content you probably need to make use of additional libraries and other other code elsewhere to the plugin. But that would be a task for you to study all code of the plugin to understand how the different parts work together and how to add additional functionality.
Yes, I am using the File Viewer plugin at https://elgg.org/plugins/2648090, but it's not showing the content because it sends the download URL to the render engine using the function elgg_get_download_url($file). This function is not returning a value.
I resolved the issue. In my version upgrades, the 'filestore::dir_root' metastring string value did not get updated to the new filestore location. Bullocks!
- C0Rrupt replied on the discussion topic Setting and Retrieving Current Variables
- C0Rrupt replied on the discussion topic Setting and Retrieving Current Variables
- C0Rrupt added a new discussion topic Setting and Retrieving Current Variables in the group Plugin Development
I don't know enough to know if there's any way to save a session id persistently over AMD requests.
What about using cookies? Would that be a possibility to save a session id on the client side to identify the session?
I considered cookies, but I don't think they're as reliable as I would like. People can disable cookies in their browser. Isn't the JSON option like server-side cookies? I went this route and it seems to be working. An added bonus is being able to persist across sessions so one can resume in the space that one left last time.
Are there concerns about using the JSON approach? It seems pretty secure, but I'm not a student of security best- practices.
@C0Rrupt Use Web services