This page has been translated automatically
We want to provide you with the latest help content in your language as soon as possible. This page has been translated automatically and may contain grammatical errors or inaccuracies. We want this content to be useful to you. Please let us know at the bottom of this page if this information was helpful.
View the original article in Russian: Руководство по использованию профиль-папки
Profile-folder is an alternative way to save a profile. During normal saving after very long use or frequent visits to certain sites, the profile file can “bloat” in size, which can lead to very long downloads and saves. First of all, the profile folder is aimed at solving such problems.
How to build a profile
Prepare the path, in the same way as it is done when saving a profile (for example, base_directory / random_string) The main difference is that the specified folder will be used for saving, not the file.
Use the Launch Instance action
It is required to select “Chrome” and check the box “Use path to profile-folder”. There must be a checkbox “Create folder if it doesn’t exist”, otherwise the absence of necessary files in the folder will be interpreted as an error, and the red line will exit.
Walk up profile
Saving:
If you do not need to save variables / proxies, then you do not need to do anything else, the profile will be saved automatically when you restart the instance, close the program, or when the project ends.
If you need to save variables / proxies, then you should execute the cube “Save profile-folder”.
Overuse of this action is not recommended. The best way to call is Bad end / Good end.
How to use profile folder
It is recommended to use a browserless project so that system resources are not wasted on launching a “standard” instance that will not be used anyway.
The subsequent actions are similar to “feeding”, with two exceptions:
The logic for preparing the path is different (it should not be generated, but selected from the already created ones).
The checkbox “Create folder if it does not exist” should be disabled, because profile-folder must already exist. The absence of a jackdaw will allow you to correctly handle exceptional situations of the absence of a ready-made profile along the specified path (an exit will occur along the red line)
Please note that only one browser instance can be launched in a specific profile folder at any given time. An attempt to launch two (or more) instances in the same profile folder will result in an exit on the red branch.
Transition from old format (profile-file) to profile-folder format
The transition from the old format should be done instead of step “3. Walk up profile” from the first part of this article.
That is, after launching the instance with the profile-folder settings, you can load the existing regular profile (the “Load profile” action), and then simply save the profile-folder.