Custom Query (1173 matches)


Show under each result:

Results (124 - 126 of 1173)

Ticket Resolution Summary Owner Reporter
#5508 cant-reproduce Allow users to upload source files alongside media Alex Jordan

Given MediaGoblin's focus on free culture, etc., it would be really cool if it had some support for uploading source files alongside "finished" media. For example, 3D model source, an archive of a video project, etc.

It seems to me that probably this makes sense as basically additional file(s) associated with one "upload" but I haven't really thought through the design that much.

#54 FIXED Ambiguous README wording Daniel Neel
The main README file for the project contains the following

"\* A place for people to collaborate and show off original and
creations Free, as in freedom. We're a GNU project in the
making, afterall."

The confusion is in the wording "...derived creations Free, as in
We're a GNU project..."

It seems this is a typo and there should be a period after
"creations", or
the words "that are" placed after "creations". Depends on the
intent of the
statement, which I'm not sure of.

#231 WONTFIX Ambiguous mongodb version dependency Caleb Davis Caleb Davis
I unwittingly triggered an extra MongoDB version dependency because
I was running MongoDB v1.2.2 on omgmg (bad Caleb, bad!). The
symptom is as follows:

-  media items show up on root.html, but the link to
   /u/this-is-my-slug gave 404 errors. However, the
   /u/objectid\_string link worked. That is, until later Elrond found
   one for which the slug link 404'ed and the objectID link 500'ed. I
   don't have the traceback.

Chris investigated, figured out the problem was probably a MongoDB
version issue, cleaned up the mess by upgrading MongoDB, and
narrowed the issue down to older MongoDBs not being able to drop
indexes...or something like that. The exact cause remains unknown,
but what is known is that there is another MongoDB version
dependency lurking in the inky shadows somewhere between v1.2.2 and

If the dependency is met by v1.3 then the docs are correct.
Otherwise the docs are incorrect.

We could narrow down the version dependency in two ways:

1. Actively by stepping through MongoDB releases on one machine
   from v1.2.2 until the ambiguously defined issue is resolved.
2. Passively by keeping an eye out for this error in IRC, and
   asking users to report their MongoDB versions here before

I'm happy to do `#1 </issues/1>`_ using the old omgmg envball and
Chris's 404 test (below). Meanwhile please consider #2.

test -
` <>`_
gives 404 error. First MongoDB version without the 404 error meets
the "dependency." That's the best I can think of for now.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.