Thank you @m_adam it's really helpful! I was going to a wrong direction. I chose to do a project that has every new aspect to explore :)) I will for sure disturb you in future with my questions. I appreciate your suggestions. Parvin

@a_block Hi Andreas, Thanks for your help and you are never too late! That actually makes more sense. Unfortunately I can't seem to replicate the issue again on my machine, as it seems that it's been working for all my updates. I will have a look on one of my team machines when released and see if that could be the problem. Thank you again!

Hi @lasselauch as @mp5gosu this is a urrlib2 issue and we can't provide support on this topic. Moreover, if you have more questions (while I think everything is said), please open a new thread since while the overall topic is related, the question and issue are different. Cheers, Maxime.

@m_adam Thanks for your help and look forward to the improvement of python doc

@m_adam Wow, this is truly great. What a fantastically written response, I really appreciate it! Learning a bunch from this example, way more than I asked for. Thanks again Jenny P.S. if only the py4d documentation had examples like this, we would all be better programmers

Hi @dev-vfxboat, first of all, welcome in the plugincafe community. This is a known bug and already fixed for SP2 (the next Service Pack). It's impacting both Python and C++. The workaround is to pass the flag c4d.SAVEDOCUMENTFLAGS_DIALOGSALLOWED to the SaveDocument function. Moreover, don't worry, but please make sure to read and use How to Post Questions (Especially about tagging system) Cheers, Maxime.

Hey @darrellp as you figured out, it was not on the correct category. But in any case don't worry, maybe I was too harsh and unprecise, I'm sorry about that but in the end, as I said, you are new here, so don't worry if you break the posting rules the first times :)

Hi zhhm156, so for coming late here, but it took more than expected. After getting in contact with the team in charge of the development and making some further researches, it appears that the VerifyServerOnClient function is indeed deprecated. I'll get back on this discussion in the future to notify about potential workaround to achieve a similar functionality. Best, Riccardo