Files in Folder disappearing

Go to the Admin/Find Content page and edit one of the files you uploaded and check to see if the Space and Section fields got filled in correctly.

Also, are you using the menu-based or taxonomy-based folder structure? If using menu-based when you edit the file page, check the menu settings to be sure it has a parent item. Also edit the Section and be sure the section page is in the Group Menu. If using taxonomy-based, check the file page to be sure the taxonomy term got set to the parent term.

Also, be sure you are not using the "Back" button in your browser to look at the page. Try refreshing the page. The AngularJS App that displays the folders won't refresh when you use the Back button.

If you still have trouble, you'll need to post an exact step-by-step procedure for reproducing it. And also mention if this is a clean install of 2.32 or if you upgraded an older version.

Curious if this was in a new install of 2.32 or was the Section created in a previous version? New sections *should* be added correctly to the automatically in the latest version.

I have the same issue.
I managed to figure out that in my case it is a problem with a space blueprint.

- I created a blueprint of space with file section inside
- I created a new space using blueprint
- File section in the new space has Menu options/Provide a menu link = OFF

I am experiencing very similar behavior as rschaeffler's initial post.

Despite this, the site is recognizing that the files were added and they appear in "Recent Documents".
Also, the folders and files show up without refreshing as the ajax calls appear to be working, just not after the page is reloaded or returned to after navigating away.

The files are properly listed in Find Content as being in the section and space to which they were added.

However, the section itself is reporting "No files to show."

I'm not using a blueprint in this space like pgancarski (was going to make the space the blueprint once I had thoroughly tested its features).

Any thoughts on what else could cause this behavior?

Kevin M.

See #4. Edit your SECTION page and make sure the Menu Link is set to . There is a bug that when a section is created via the Site Map, the parent is set to the Main Menu instead of the Group Menu.

So you know that you can use a taxonomy-based Folder scheme instead of the default OG Menu-based scheme, right? If you look at the widget options you can change it from Menu mode into Taxonomy mode. Then you have folders based on taxonomy terms and it won't mess with your OG Menu.

I'm not sure how else to make adding files/folders easier since there are big buttons on the page for "Add Files" and "Add Folder". And the gear menu for each folder has "Add Folder" for creating subfolders. Your users shouldn't need to mess with the menu settings at all (except for the bug mentioned in #9).

If you just set the Section itself to be "Disabled" in the menu, then none of the subfolders will show up. So I guess I'm still a bit confused on how you are using this menu and how you'd expect to manage these things.

(And just to re-interate: The fact the items are added under the Main Menu instead of the OG Menu is a bug and will be fixed in the next release)

I knew I fixed this bug a few months ago. #2424785: Group context not set on wizards, group menu not set, but it was missing one line

include_once 'includes/oa_core.context.inc';

in the top of oa_core.module

I'm not sure exactly what happened -- whether I never committed the include of this file or it somehow got overwritten/lost at some stage.

@hefox , is this fixing the same issue with blueprint spaces as well? Comment #7

I'm having the same situation like #7

Thanks

My case is similar, but a different issue I think, because in 2.33 to create through sitemap it works, but not when you make space blueprint with file section.

Working with 7.x-2.41 looks there are still issues here. For one the Document Page edit page doesn't display the Vocabulary widget by default, making it impossible to attach a term to the page. With this changed, when the terms are added the folders appear but the files aren't displayed in the folders. This does happen when the Files & Folders widget is set to "Section: None". So somehow the "Section-awareness" doesn't seem to work.

I noticed that the openatrium website is acctually broken.
See the Documentation menu
http://docs.openatrium.com/documentation/how-add-menus

Argus, is that what you mean when you say that folders appear but files don't?
It looks to me like the documents are being shown as folders.

I had files added to a folder, but they wouldn't show up, the file count remained zero, but I cannot reproduce that, so it might not be an issue after all.

This might be a different bug:
https://www.drupal.org/node/2484677
Try adding them with the plus button in the top (breadcrumbs) menu.
This was a problem in the previous versions, and I believe it was fixed in 2.41

@Argus wrote:

the file count remained zero

Yep, this - at first sight - is still happening on OA 2.43 but, once the page is reloaded (going away and returning or just by reloading it through the web browser), the counter fixes automatically - from (0) to (n) - the number "n" of files that actually belong to the folder.

I fixed the file count issue, if anyone wants to manually test it, check out http://cgit.drupalcode.org/oa_files/commit/?id=7eb096903e465070ab647a537...

That commit worked for me, thank you @hefox.

Ive had the same issue than #1

Now I use the taxonomy-based folder structure and its working like a charm.

But there's still a problem using the native method

Just an update: still happening on OA 2.45 (upgraded from OA 2.43), as @mpotter wrote in #9:

There is a bug that when a section is created via the Site Map, the parent is set to the Main Menu instead of the Group Menu.

That bug is still present.

Once on the Files Section the Menu Options is enabled by checking "Provide a menu link" you will discover that Parent is not set (if the Files Section was created through the Site Map, as noted): once Parent is set to Group Menu then files and folders previously created will appear BUT folders created with files placed into them *before* fixing the Parent parameter will be displayed as separate nodes: as document nodes on root (for Folders) and as files on root (for Files even if they were initially nested into one or more Folders). Folders and Files created *after* the manual fix are represented correctly.

Edit: fixed text formatting that hid the word Group Menu rendering the statement "...once Parent is set to "" then..." wrong; now it's correct.

Hi,

I'm facing the same file issue.
- file is uploading and displaying at first time.
- after refresh, the uploaded files are not displaying...

There is a bug that when a section is created via the Site Map, the parent is set to the Main Menu instead of the Group Menu.

I cannot reproduce that bug anymore. Can you try creating a new Space and then a new Section to reproduce this? Check to be sure your Space is not set to the Main Menu. Also, in your Structure -> Content Type -> Space, edit the Menu options and make sure in the "OG Menu Single" fieldset that the "Content of this type may be placed in a group menu. Must also be a group content type" is UNSET and the "Groups of this type may have a group menu. Must also be a group type" is SET.

soorepalli: You need to read this whole thread and check your Space and Section menus before reporting a bug.

If somebody reproduces a problem on a fresh install of 2.45 then you need to post the exact steps to reproduce it. If you are upgrading an older site then it's likely your space and/or section nodes are not set to the correct menu. Upgrading Atrium can't fix that for you. You need to test by creating a new top-level space, and then a section within that space to ensure you are not getting bad menu values from old pre-upgrade content.

Mike, can you clarify the part about the *fresh* install of OA 2.45?

I checked on a *upgraded* OA 2.45 (from 2.43) which showed the issue and, on admin/structure/types/manage/oa-space (those on the Menu settings of the OA Space Edit page), both settings:

• [Disabled] Content of this type may be placed in a group menu. Must also be a group content type
• [Enabled] Groups of this type may have a group menu. Must also be a group type

appear to be set like you asked to verify (so no difference between OA 2.43 and OA 2.45 upgraded/fresh installed).

Note: Available menus setting shows that only Main menu is enabled and Default parent item is set to .

Am I missing something or basically, up to now (at least up to next OA 2.50), we need to manually fix the correct menu as per #9 for existing Spaces because, as you said, upgrade will not fix that part?

As I understood with the upcoming OA 2.50 the issue shall be fixed for *new* created spaces *only* (if OA is upgraded from a previous version no matter if a manual fix as per #9 was executed) or it shall be fixed for *all new* created spaces (if OA is a fresh install)...or it is yet fixed on fresh install of OA 2.45 too? Sorry for confusion but I need to be sure to have understood the sequence of events.

By "fresh install" I meant: Install a new Atrium 2.45 site on Pantheon and if you can reproduce the problem, post the exact steps.

There is no way to automatically fix any existing spaces that might have incorrect parents. In 2.50, any new space and section created in the sitemap should have the correct menu and parent set. However, if you create a subspace or section within a previously existing space that is messed up, then the subspace and section could also be messed up.

Thanks Mike, now it's clear for me. Thanks again.

Thanks mike, With fresh installation of 2.45 the files section is working fine.