Send private message

You must be logged in to send a private message.

Friends

No friends yet.

Group membership

Activity

  • C0Rrupt replied on the discussion topic Implementing elgg_file_viewer extension
    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! view reply
  • C0Rrupt replied on the discussion topic Implementing elgg_file_viewer extension
    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... view reply
  • C0Rrupt replied on the discussion topic Implementing elgg_file_viewer extension
    Update:  I'm still on 2.3.16.  The issue stems from the function elgg_get_download_url($file) not returning a value.  I understand that the function only works on a standard filestore. How does one determine whether... view reply
  • C0Rrupt replied on the discussion topic Implementing elgg_file_viewer extension
    OK.  I figured out that, as an extension to the File plugin, one must use the file plugin to render the file thusly: elgg_view_entity($file);  Having figured that out, I get an "Error 400 (Bad Request)!!1" error... view reply
  • C0Rrupt added a new discussion topic Implementing elgg_file_viewer extension in the group Beginning Developers
    I want to use the elgg_file_viewer extension to render the contents of files inline, but I don't see any functions, classes or methods that I should use.  I would expect to implement it using something like, "echo...
    • 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
    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. ... view reply
  • C0Rrupt replied on the discussion topic Setting and Retrieving Current Variables
    "Session" might not be what I was looking for.  Elgg's session object does not seem to store the current_space_id for AMD requests between page refreshes.  Is there a way to store the variable more persistently? ... view reply
  • C0Rrupt added a new discussion topic Setting and Retrieving Current Variables in the group Plugin Development
    My elgg installation allows a user to create separate spaces and to use objects within each space independently.  A new object should use the space as its default container.  I think I would like to set the space in the session...
    • 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.