- "There is no API keys found in the API login backend, Kindly let me know the editmode javascript link to be added in the header and how the site's getting differentiated without API keys."
- The js file asks the user to log in with a username and password when they hit the keyboard shortcut. This step is skipped on the demo website for demonstration purposes, but you can see it if you go to www.editmode.app and hit CMD&SHIFT&E
- 
- "Writing functions in the layout for 1) displaying chunk, 2) get chunk collection, 3) Property of chunk. These functions should be written in the plugin or in the layout files."
- I’m not 100% sure on what the difference is. I would ideally like other people to be able to easily add the functionality to their wordpress install without modifying code, so I think the Plugin store would better allow them to do that? I read this post which gave me the understanding that was possible https://codeaddiction.net/articles/50/custom-wordpress-shortcode-plugin---tutorial--howto
- "I need the list of API links to call from the site."
- Collection: https://www.editmode.app/api/v1/chunks/?collection_identifier=XXXXXX
- Single Chunk: https://www.editmode.app/api/v1/chunks/XXXX
- Right now all chunks on the platform are public, so there’s no authentication for these endpoints.
- What functionality to be written in the route files for clearing cache - “/editmode/clear_cache?identifier=CHUNK_ID”
- You can see the Rails code here: https://github.com/tonyennis145/editmode-rails/blob/master/app/controllers/editmode_controller.rb
- "For better understanding, Kindly let me know what are the steps followed to build in ruby on rails in order wise, if you can?"
- Here is the main rails gem repository: https://github.com/tonyennis145/editmode-rails
- The main files are:
- View Helpers https://github.com/tonyennis145/editmode-rails/blob/master/lib/editmode-rails/action_view_extensions/editmode_helper.rb
- Routes: https://github.com/tonyennis145/editmode-rails/blob/master/config/routes.rb
- CDNJS includer: https://github.com/tonyennis145/editmode-rails/blob/master/lib/editmode-rails/auto_include_filter.rb
- Cache Controller: https://github.com/tonyennis145/editmode-rails/blob/master/app/controllers/editmode_controller.rb
- "I have analyzed the process of cache holding and updating from the sources. It seems to be difficult with working in caching the data with php codes and also I've checked the API backend and there is no options like token key generation for accounts for addressing and it has only the project adding form. So it may be fine if tokens could be generated from backend rather than url for accounts and projects. Can you able to setup the token key generation at the API backend in order to achieve this functionality."
- I don't fully understand the question. If you mean authenticating before expiring the cache, the proof of concept app won't authenticate the request. It'll just accept a simple get request with a cache key - the cache key is the identifier of the chunk. We won't have caching yet for chunk_collections, just single chunks. I think some of the links above will help to further understand this.