Hi Vincent, this touches on something we at Legion GIS came across
recently, while trying to include file pathsd in a CSV upload. Turns out
that because the actual upload process isn't run, even if the files exist
in the file system before the import their status is never updated to
"uploaded". Our first work around is a management command that goes in
after the fact and manually changes all statuses to "uploaded".
This is only tangentially related to your question, as it doesn't address
the "queued" value, but I wanted to mention it because ultimately we too
are wondering what the status property is for...
On Thursday, October 11, 2018 at 3:06:05 AM UTC-5, Vincent Meijer wrote:
>
> Sometimes after I uploaded a file and then try to display them in the
> frontend, the item has a status 'queued', where I would expect the status
> to be 'uploaded'.
> This property is used e.g. in the Image Header template (image.js):
>
> if (item.status &&
> item.type &&
> item.status === 'uploaded' &&
> item.type.indexOf('image') > -1 &&
> _.contains(nodes, key)
> ) {
> imgs.push({
> src: item.url,
> alt: item.name
> });
> }
>
> I am using a similar approach on a custom template to read file names of
> uploaded zips:
>
> if (item.status &&
> item.status === 'uploaded' &&
> (item.name.split('.').pop() == 'zip')
> ) {
> potreeZipFiles.push({
> src: item.url,
> name: item.name
> });
> }
>
>
> What is the function of this status property and why does it still have
> the 'queued' value while the upload has already finished?
>
>
--
-- To post, send email to [email protected]. To unsubscribe, send
email to [email protected]. For more information,
visit https://groups.google.com/d/forum/archesproject?hl=en
---
You received this message because you are subscribed to the Google Groups
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
