add a file option not working

I have a paid storage account with about half a gig remaining on the current plan.  At the moment I am unable to attach files (mainly PDFs) to any item in a recently created library.  Neither the drag and drop or the manual attach a file options are not working.  When I right click on an item the attach a stored copy option is deactivated.
  • It’s an open public group, which doesn’t allow file sharing.
  • No, the situations also apply to the group libraries. We do not even attempt to post files to the CRTc Online Library just citation info. For example, the LIS 759 library has three members and the issue persist there as well. So, again, no, the issue is beyond "open public group" library.
  • dstillman Zotero Team
    edited August 15, 2024
    You don't seem to have read what I said. This is entirely about group libraries. LIS 759 is a public open group, so it doesn't allow files. You can see this in the group settings.
  • Oh, I understand. I can read, but thank you for the condescending sarcasm. The LIS 759 is in the same space as group libraries: LIS 885, LIS 801, LIS 762, which have attachments. All of these libraries are under "CRiT Community," which has multiple libraries with attached files.
  • Every group library has separate settings. As dstillman says, LIS 759 is public, open.

    https://s3.amazonaws.com/zotero.org/images/forums/u2433/upyr3q7g36ck90aklqdb.png

    LIS 885 is public close, and as such can have attachments. There is no such things as libraries "under a community"
  • thank you for the condescending sarcasm
    It wasn't sarcasm. I said it was an open public group, and you responded by saying “No, the situations also apply to the group libraries” and listing the group that is an open public group.

    To be clear, this is all covered in the groups documentation and in the group settings, both when the group is created and any time after that.

    This is your first time posting here, but I would ask that, in the future, you consider that you might just be misunderstanding something and not jump to the conclusion that things are broken (and not insist that we're obligated to provide you with support via a medium that we specifically say we don't use for support because your paid plan was "not functioning"). You should also generally assume we know what we're talking about when we give you answers instead of insisting that we're wrong.
  • Let me also be clear. Incomplete answers are just as useless to marginally useful as "wrong" answers. Your word not mine. There wasn't an assumption that things were broken, but there was a frustration level; first, with the situation then dealing with you (dstillman). Now the additional frustration level of not only, yes, your condescending sarcasm but this added level of snide arrogance. Perhaps, while being quite impressed with yourself consider how you might be coming across in spaces outside your own ego. Being knowledgeable and being helpful are two different aspects to service. Because the you perceive information seeking behavior in a certain way does not mean it always translates or plays out the way it is intended.

    Adam, thank you for the point of clarity and the competence of sharing the screenshot. That was far more helpful.
  • There wasn't an assumption that things were broken
    "not working"
    "Up until now, Zotero has been relatively problem free"
    "paying for an option/ that is currently not functioning should move beyond your statement, "we do not provide technical support by email.""
    Incomplete answers
    I quite literally answered your question, with the standard response we give people when they're confused by this. They usually respond with "Ah, got it — thanks", so we don't find it necessary to elaborate. You're welcome to ask clarifying questions if you don't understand something. Your approach was to insist that I was wrong. You came here frustrated, demanded special attention via email, and dismissed me when I gave you the correct answer.

    Please rethink your approach before posting here again.
This discussion has been closed.