Hello,
Our hosting provider recently updated our package, which broke all the Groups File Access links.
Old Path: /home4/{username}/public_html/wp-content/uploads/groups-file-access/{filename}
New Path: /home3/{username}/public_html/wp-content/uploads/groups-file-access/{filename}
Is there a reason you are going so deep in the file paths? Why not make the part up to public_html relative?
Thanks for mentioning Rodd.
The Migration guide you found is related to migrating from the old model of Groups (capability-based) to the new one (Groups based). But despite that, your search should have given you the migration guide specifically for Groups File Access migration and this is the point of interest worth checking for us.
Kind regards,
George
Ok, thanks. I did check the documentation first.
I went to the root page first and didn’t see anything or a link on the menu.
https://docs.itthinx.com/document/groups-file-access/
When I searched your documentation for “Migration” I got
https://docs.itthinx.com/document/groups/migration-guide/
I would suggest adding all plugin migration information to the Migration Guide page, so if a user is moving, they have everything they need in one spot.
Hey Rodd,
The reason for using the absolute path is because it can be tricky to find the current location and use it as relative path to public_html or any other public folder the webserver can be using( public_html is common to apache setups only ). However, I’ll explore the available options once more and promise to check whether this is possible to avoid using the absolute path in place of something more simple.
In the meantime and in case you haven’t noticed, there is a guide in the plugin documentation you can use when migrating to a new server:
– https://docs.itthinx.com/document/groups-file-access/file-access/
under the section Moving to another Server.
Kind regards,
George