Last modified: 2014-02-22 21:36:10 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 27306 - Need a dedicated storage interface for extensions
Need a dedicated storage interface for extensions
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: documentation
  Show dependency treegraph
 
Reported: 2011-02-10 19:27 UTC by paxed
Modified: 2014-02-22 21:36 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description paxed 2011-02-10 19:27:52 UTC
There's no preferred/suggested MW way for extensions to cache the stuff they generate. For example, EasyTimeline writes the generated images into $wgUploadDirectory."/timeline/", and there's also $wgCacheDirectory...
Comment 1 Platonides 2011-02-10 20:28:57 UTC
For small data, they should use $wgMemc, so this is about having some standard for extension cache files...
Comment 2 Bryan Tong Minh 2011-02-10 20:31:11 UTC
(In reply to comment #1)
> For small data, they should use $wgMemc, so this is about having some standard
> for extension cache files...
I believe this is more about things that need to be embedded in the wiki page like math images, timelines, music scores, etc.
Comment 3 Quim Gil 2013-03-18 06:19:24 UTC
CCing Sam just in case there has been any discussion about this. I couldn't find any guidelines in the developer documentation.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links