| Age | Commit message (Collapse) | Author |
|---|
|
the url to dictate arbitrary static method calls.
* Each xxx_rss helper has a single feed() call which takes an id as the argument
* xxx_rss::available_feedS() only returns feeds when they're applicable (ie
if you're viewing a tag, it won't show you an item feed).
* Feed urls are now in the module/feed_id form so that we can bind a
feed id to a given module
* Tightened up the Rss_Controller by using url::merge and some other tricks.
* Made the slideshow module express its own feed.
|
|
max-pages calculation code. Move feed related data into the $feed
variable and only pass that to the view.
|
|
|
|
replace with a type field with one of two values (head and block). We need to
do this to determine what fields go in the rss block so we can ignore the
definitions that are related to the page head when creating the rss block that
goes into the sidebar.
|
|
functionality in the <module_name>_theme::head function. Created rss::feed_link
to wrap the module supplied uri in the html link element.
|
|
rss::get_feeds() -> rss::available_feeds()
rss::process_feed() -> rss::feed_data()
|
|
url to rss/feed/<feed name>/[<id>]
Where feed name is the name of the feed (i.e. albums, updates, comments, tags
etc.) and id is the optional element id that the feed applies to.
|
|
tag feeds to the gallery and tag modules respectively. This chould close
ticket #388
|
|
modules that are supplying the feed. The rss controller becomes a router.
In this change the comment and updates fields are distributed.
|
|
api.
|
|
provide the part of the url (the suffix) that they are interested in and the
rss module will format the rest of the url.
|
|
|
|
allow modules to contribute rss feed links to the rss sidebar block.
Ticket #388.
|
|
|
|
|
|
|
|
Install: <module>_installer::install() is called, any necessary tables
are created.
Activate: <module>_installer::activate() is called. Module
controllers are routable, helpers are accessible, etc. The module is
in use.
Deactivate: <module>_installer::deactivate() is called. Module code
is not accessible or routable. Module is *not* in use, but its tables
are still around.
Uninstall: <module>_installer::uninstall() is called. Module is
completely removed from the database.
Admin > Modules will install and activate modules, but will only
deactivate (will NOT uninstall modules).
|
|
|
|
|
|
|
|
case that a gallery is slightly corrupt. In that case, just ignore
the error.
|
|
|
|
which fall through to calling &View::__get() have an lvalue to return,
else you can't return them by reference.
Also, don't show sidebar blocks for pages that don't have an item so
that the rss and tag modules don't break the search page.
|
|
|
|
max_page, just return an empty feed.
|
|
|
|
|
|
how to embed the object in the feed, so the recieve will still have to
click on the thumbnail to see the move. Instead of actually playing
in the feed reader.
|
|
yet, but that's maybe because I'm not generating thumbnails
|
|
|
|
2) Created a comments feed (/rss/comments)
3) Created a updates feed (/rss/updates)
User interface to follow
|
|
|
|
of the message in the feed reader.
|
|
2) Protect the fullsize image with a permission check
3) Added a content:encoded element to each item which allows the image to show up in the body of the feed.
|
