-
Notifications
You must be signed in to change notification settings - Fork 95
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
Could not created .... #103
Comments
Are you able to run the exporter on the CLI? I have no idea why the recursion happens. Maybe you have somewhere a symbolic link on the disk which is recursive? |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
OK now I ran it for a 3rd time using PHP8.1 (which I should have run in the first place, sorry for the confusion). Now I get the same error message as when using Wordpress plugin in the admin panel... Ps. I got the same issue when using Cause?
Full output:
|
This comment was marked as off-topic.
This comment was marked as off-topic.
I also noticed that wp-content/uploads is getting copied by the exporter. And within that folder a new wp-hugo-xxxx folder appears, with a different hash?? If people use your exporter plugin within Wordpress, there will be a new folder in the uploads directory, right? So I think I found the recursive problem. Which is part of your tool, if you don't ignore your own wp-hugo created folders in the |
When going to
wp-admin/export.php?type=hugo
and after a while.. I think the export is done?...But your plugin will show an error message on the screen:
Looking at the Nginx logging, this will give:
Which is not really helpful at all.. But it seems it tries to copy and move files to the root folder, I guess it's a bug of the exporter.
The text was updated successfully, but these errors were encountered: