#130 - Foolproof content embedding
-
By Chris Graham
- Added
- 3 views
| Identifier | #130 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Foolproof content embedding |
| Status | Completed |
| Tags |
Roadmap: Sponsorship (custom) Type: Cross-cutting feature (custom) Type: Usability (major) (custom) |
| Handling member | Chris Graham |
| Addon | core_rich_media |
| Description | I'd like the block wizard to be able to be able to easily select almost any content type category or entry, and embed it into a page. This would use the main_content block.
- Make the block wizard be able to browse the whole site-tree to pick out content to use - Test every content/category type |
| Steps to reproduce | |
| Related to | #131 - Unified top/recent system #35 - Full breadcrumb customisation on frontend, via XML #448 - Extend new grid layout to function in main_multi_content block |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
1) Make more Composr screens consist of AJAX blocks, hard-code less into specific modules, make templates glue it together. E.g. on the filedump screen, the actual file dump listing would be a block embedded into the page template. i.e. most of the page code is moved into a block, and the page itself becomes mostly glue.
2) Use the new 'HTML5' 'server sent events' API (if we can) to sent events indicating a block has changed and needs to be refreshed. E.g. upload to filedump, so filedump-file-list anywhere will see event and refresh. Improve Tempcode to make this automatic when $BLOCK is used. The events would be a side-effect of writing to the action log.
3) The get_self_url function should work for non-index scripts so that it is really easy to create links regardless of whether it is a page or a script.
4) Remove the concept of 'wide_high', use a new URL param to decide whether to use 'STYLED_HTML_WRAP' or 'POPUP_HTML_WRAP' or 'HEADER'/'FOOTER' or raw text is output.
EDIT: Ignore the above, there's no real expectations for pages to do live updates for CMS content - and it could cause issues. 3/4 was kind of done in v9.
I didn't know you couldn't be able to be able to :P lol just teasing you about the typo.
Also, in terms of auto updating content, perhaps take one of my implementations on lovinity.org for forum posts and tickets. I replaced the auto load with instead an overlay message that pops up informing the user that the content has changed. That way, the user can choose whether or not to refresh, and if so, can copy their reply text or what have you so it's not lost in the refresh. Perhaps make it a choice/option for use.
Thank you for your sponsorship again Rishi.