You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
I have an issue with the packager. When I've try to load lot of plugins, the packager just load the first 11 and the others are omitted, so when the result OCS package is installed in a client, just create plugins with this first 11. If I open again the "View/modify Plugins..." button, the 12th path is "cutted", so I understand that for this cause, the agent omitted others plugins.
And when I load a cacert.pem file in OCS Packager, doesn't copy any file, and the agent config file uses the folder of OCS package Certificate file. I assume that packager sould do the same with ther certificate like with plugins, copy the file to default folder and then point it in config file. But in this moment doesn't
The text was updated successfully, but these errors were encountered:
Same here.
Workaround:
Put the plugins in a folder with a single character name and directly at the root of a disk.
As a result, the file paths of the plugins are shorter, and you can put more (18 for me).
Hi!
I have an issue with the packager. When I've try to load lot of plugins, the packager just load the first 11 and the others are omitted, so when the result OCS package is installed in a client, just create plugins with this first 11. If I open again the "View/modify Plugins..." button, the 12th path is "cutted", so I understand that for this cause, the agent omitted others plugins.
And when I load a cacert.pem file in OCS Packager, doesn't copy any file, and the agent config file uses the folder of OCS package Certificate file. I assume that packager sould do the same with ther certificate like with plugins, copy the file to default folder and then point it in config file. But in this moment doesn't
The text was updated successfully, but these errors were encountered: