Update IMG Size Bug

[netspy]

It seems that the "Update IMG Size" function does not respect the Root Folder in project settings. I have this folder structure:

/www/project/html
/www/project/html/content
/www/project/html/images

The Root Folder is /www/project/html. If I edit a HTML file in the /content folder and insert an image with src="/images", WeBuilder can't update the image size and show the message that the image was not found. The "Update IMG Size" function works only, if I set a relative path like src="../images".

Could you please fix this bug?

[Karlis]

How can one tell your project root folder by only looking at the open HTML file?

This is not a project feature, but file-related feature instead, so it only looks at the current file, not project settings.

[netspy]

How can one tell your project root folder by only looking at the open HTML file?

If a project is opened, I expect the project root folder to be respected by folder specific functions.

This is not a project feature, but file-related feature instead, so it only looks at the current file, not project settings.

That's unfavorable. Many web developers use templates and the template files often are not located under the HTML root folder. So the IMG size feature of WeBuilder cannot be used.

I know this useful function from TopStyle Pro where the IMG size feature follows the site (project) settings.

[Karlis]

I can consider this as a valuable feature suggestion to be added to wishlist. I'll check how difficult would be to add this.

[netspy]

I can consider this as a valuable feature suggestion to be added to wishlist. I'll check how difficult would be to add this.

No changes in WeBuilder 2007.

[chrisjlocke]

Isn't it good practice to use relative file names anyway, rather than absolute?
That way, if the files have to get moved to a different structure slightly (eg, your website gets moved into a 'newsite' folder) everything still works.

[netspy]

As I described above I use (as many other web developers) templates and the template files often are on other locations than the document in the URL. Popular examples are blogs like WordPress.

As my images are allways located under the path /images, there is no problem, if I change the file location of my documents. The absolute path is still correct.

[Karlis]

We did not have time to add this, we have to add zillion of features every year and since this is not highly requested, it is a low priority.

[netspy]

Implementing this "feature" is not very expensive. First, you search (as it is done) the image relative to the location of the html file. If no image is found, you search it relative to the project root folder.

I can't believe that takes more then 10 source lines.

[Karlis]

We do have many easy 10-line features waiting in line, a few hundreds of them, however still there must be order, chaotic approach will lead development to halt

[ginestra]

Add me to the 'would like this feature' list please. I use root (as opposed to document) - relative links on all projects, for all sorts of reasons.

Am a recent convert to WeBuilder, having used Dreamweaver for years, but one good thing about DW was that on the 'insert image' or 'add link' browse dialogue, you had the option to select either 'root relative' or 'document relative' when the path was written. This was a sticky setting, so it stayed at whatever was last used.

Have always preferred the convenience of /root/relative/links and would like to not continuously have to manually remove the likes of /./.../. after links are coded.

Thanks