Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get all Public Folders #1300

Open
dtalkachou opened this issue Apr 22, 2024 · 7 comments
Open

Get all Public Folders #1300

dtalkachou opened this issue Apr 22, 2024 · 7 comments

Comments

@dtalkachou
Copy link

Previously we retrieved all public folders for an account by account.public_folders_root.root.children. But it doesn't work for about three weeks, it returns an empty generator. Even though account.public_foolders_root.child_folder_count returns the number that matches real public folder numbers, we still cannot find a way to iterate through all of the IPM folders as we did before. We use version 4.7.2 but don't mind switching if it helps. Does anyone can help us?

@ecederstrand
Copy link
Owner

I think this is connected to the issue reported in #1273.

I don't have access to a test account with public folders, so I would suggest to debug this as described in #1273 (comment)

Please note that it would help if you debug from commit f65079f which is still unreleased, since there were changes related to public folders in that commit.

@dtalkachou
Copy link
Author

@ecederstrand I think it's somehow related because appeared about the same time, but not our problem. We work with public folders and can't get a list of all IPM folders. I also noticed that the code account.public_folders_root // "folder_name" works for public folders, but our first problem is getting a list of all IPM folders as I said. Previously we did it by account.public_folders_root.root.children, but now it provides an empty generator.

I tried the commit you specified, but it's still an empty generator.

@ecederstrand
Copy link
Owner

Ok. Adding a breakpoint in BaseFolder.children() and stepping through the code is your best bet in debugging this. If you enable debug logging you should be able to see the XML requests and responses while you are stepping through the code. That might give you an idea of where the problem lies.

@ecederstrand
Copy link
Owner

Actually, there's a slight possibility that d9035d0 fixes this. Can you give it a try?

@dtalkachou
Copy link
Author

Thank you very much for your involvement in our problem, but it still doesn't solve it.

@ecederstrand
Copy link
Owner

@dtalkachou Did you find a solution to this? Is it apparent in all exchangelib versions, or is there a certain one that exhibits the error?

@dtalkachou
Copy link
Author

No, I haven't. It's not dependent on the version. It returns an empty generator since somewhen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants