Very useful plugin — two issues found during active use

Hello,

I have been actively using 4WP Drive as part of my regular WordPress publishing workflow, and I would first like to say that I genuinely appreciate this plugin.

At the moment, 4WP Drive is the only plugin I have found that properly fits my specific workflow. One feature that is especially important to me is the ability to import an article together with its images while preserving the original image filenames. I prepare my images in advance with meaningful English filenames, so keeping those filenames intact is essential for my workflow.

For this reason, I am giving the plugin 5 stars. This does not mean that I have not encountered any issues, but rather that 4WP Drive currently solves a specific problem for me better than any other solution I have found.

During active use, I have encountered two issues that I would like to report as constructive feedback.

1. New folders in Incoming do not always appear immediately

When I add a new article folder to the incoming directory, it does not always appear in the plugin interface immediately.

In my case, I sometimes need to clear the WordPress/cache before the new folder becomes visible.

It would be very useful if the Incoming view could reliably detect and display newly added folders without requiring manual cache clearing.

2. DOCX files containing tables can break the document structure during parsing

This issue took me quite a long time to diagnose because the plugin itself did not report an error.

When a DOCX document contains a table, the Preview can parse the article incorrectly. The document structure becomes broken: headings may no longer be recognised correctly, and the article can appear flattened or malformed.

The difficult part was that there was no warning indicating that the table was causing the problem. The plugin simply displayed an incorrectly parsed article, so I spent a considerable amount of time comparing working and non-working documents before identifying the cause.

I was eventually able to reproduce the issue consistently:

• the DOCX containing a table is parsed incorrectly;
• removing the table from the same document allows it to be parsed correctly;
• after importing the article, I can insert the table back manually in Gutenberg.

This workaround is simple and works well for me, but native table support would obviously be very useful. Even a warning that a document contains an unsupported table would make diagnosing the issue much easier for users.

I am sharing these observations because I intend to continue using 4WP Drive and would like to see it become even better. The plugin fits my workflow extremely well, and these comments are meant purely as constructive feedback from an active user.

Thank you for developing and maintaining 4WP Drive.