Problem with images
Posted: Mon May 26, 2025 2:18 pm
Hi,
I'm new to Bludit coming from my much beloved former phpCMS which is no longer developed since 1983. So I thought it's time to change and after trying some others, I landed in Bludit. So I try to migrate my websites.
To do that, I'm studying the documentation, but that does not always help to explain how Bludit internally works. But to find the reason for an error, it would be necessary.
1. When I include a favicon via <?php echo Theme::favicon('img/favicon.png');?> in index.php, in the quell code of the published web page I see that it is loaded there as https://mydomain.com/bl-themes/mytheme/img/favicon.png.
The same goes for any other item to be loaded from a template in mytheme, i.e. css files, navigation items, images, ...
An internal call like /mytheme/img/image.png or so would be much look much easier to me.
2. With an image added to a page it's even more complicated. When I include e.g. image.png there, that one is also fetched for the web page via an external call like https://mydomain.com..., but not as https://mydomain.com/bl-content/uploads/pages/mypage/image.png, as expected, but as https://mydomain.com/bl-content/uploads/pages/77ce995cba184fee31e4df615bd742ef/image.png.
That looks to me as to be fetched from a sort of cache. What for? To gain in speed? An internal call like /uploads/pages/mypage/image.png or so would IMO be much easier and be completed as fast.
The difficulty is the same when later I want to retrieve the image, e.g. in the MultiBlock settings. In the image folder opened there I find it not as /uploads/pages/mypage/image.png but also only with a file name with that long coded part.
And to find the uploaded image in my FTP client is nearly impossible.
Is that normal with Bludit? If so: why?
Still, Bludit looks promising for my needs, so I think I'll stay with it. Thanks to all involved for that CMS! But I'll have more questions...
Harald
I'm new to Bludit coming from my much beloved former phpCMS which is no longer developed since 1983. So I thought it's time to change and after trying some others, I landed in Bludit. So I try to migrate my websites.
To do that, I'm studying the documentation, but that does not always help to explain how Bludit internally works. But to find the reason for an error, it would be necessary.
1. When I include a favicon via <?php echo Theme::favicon('img/favicon.png');?> in index.php, in the quell code of the published web page I see that it is loaded there as https://mydomain.com/bl-themes/mytheme/img/favicon.png.
The same goes for any other item to be loaded from a template in mytheme, i.e. css files, navigation items, images, ...
An internal call like /mytheme/img/image.png or so would be much look much easier to me.
2. With an image added to a page it's even more complicated. When I include e.g. image.png there, that one is also fetched for the web page via an external call like https://mydomain.com..., but not as https://mydomain.com/bl-content/uploads/pages/mypage/image.png, as expected, but as https://mydomain.com/bl-content/uploads/pages/77ce995cba184fee31e4df615bd742ef/image.png.
That looks to me as to be fetched from a sort of cache. What for? To gain in speed? An internal call like /uploads/pages/mypage/image.png or so would IMO be much easier and be completed as fast.
The difficulty is the same when later I want to retrieve the image, e.g. in the MultiBlock settings. In the image folder opened there I find it not as /uploads/pages/mypage/image.png but also only with a file name with that long coded part.
And to find the uploaded image in my FTP client is nearly impossible.
Is that normal with Bludit? If so: why?
Still, Bludit looks promising for my needs, so I think I'll stay with it. Thanks to all involved for that CMS! But I'll have more questions...
Harald
)