Subdirectory install: /wordpress removed from asset paths

Hello,

After updating Simply Static, the generated asset paths changed unexpectedly. Environment

Before update

• Simply Static Free: 3.1.8.1
• Simply Static Pro: 1.6.0

After update

• Simply Static Free: 3.7.7
• Simply Static Pro: 2.4.9

WordPress installation

My WordPress is installed in a subdirectory.

WordPress Address (URL)

https://example.com/wordpress

Site Address (URL)

https://example.com

Simply Static settings

Replacing URLs:Relative Path

Path:

/

Deployment:

• Local Directory

Local Directory:

/www/example.com/static_directory

Expected result (before update)

Generated assets were exported like this:

/www/example.com/static_directory/wordpress/wp-content/...
/www/example.com/static_directory/wordpress/wp-includes/...

Actual result (after update)

Assets are now exported like this:

/www/example.com/static_directory/wp-content/...
/www/example.com/static_directory/wp-includes/...

The “wordpress” directory is no longer included.

As a result, all asset URLs become invalid in my deployment environment. Additional testing

I also tested the Hide WordPress settings.

When I changed:

wp-content directory
→ wordpress/wp-content

wp-includes directory
→ wordpress/wp-includes

I expected:

/www/example.com/static_directory/wordpress/wp-content/...
/www/example.com/static_directory/wordpress/wp-includes/...

However, the generated directories became:

/www/example.com/static_directory/wordpress/wordpress/wp-content/...
/www/example.com/static_directory/wordpress/wordpress/wp-includes/...

I also tested with another directory name.

For example:

wp/wp-content

and the generated result became:

/www/example.com/static_directory/wp/wp/wp-content/...

So it looks like the replacement is applied twice. Verification

I created a fresh copy of the production site and tested step by step.

• Updating other plugins → OK
• Updating WordPress → OK
• Updating Simply Static → the issue appears

So I believe this issue is related to Simply Static and not WordPress or other plugins.

Question

Is this the expected behavior in recent versions of Simply Static?
Or is this a bug related to subdirectory WordPress installations?
If this is expected behavior, is there a recommended way to generate assets under:

/www/example.com/static_directory/wordpress/wp-content/
/www/example.com/static_directory/wordpress/wp-includes/

as before?

If you need any additional information or testing, I’d be happy to help.

Thank you.