Hello Raoul,
apologies for the inconvenience.
What version did the project come from, and what is its size roughly?

2025-3 and does 1.600kb makes sense? That number is the sum of whats in the project folder

Hello Raoul,
it would be a small size for a project, though it is possible with a low amount of pages/contents.

https://www.clubtaxi.nl/en/sitemap.xml + https://www.clubtaxi.nl/sitemap.xml

everything is relative :)

each page is about 164kb * 290 pages + 1.600kb would come closer I suppose

Hello Raoul,
I assume there are also images and maybe videos in the project, however?

Has the conversion finished, or is it still loading?
If you still need to convert one of the versions, could you provide a copy to me so that I may also attempt it?

and version was 2026.1.1

Ànd the project keeps crashing, reinstalled the software, but it hangs again in the conversion. Sweating under my arms, again a day as good as lost.

Hello Raoul,
could you please provide me with a copy of your projects' folders?
I will attempt the conversion and examine the errors if they occur.
By default you can find them at C:\Users\YourUsername\Documents\Incomedia\WebSite X5 - Pro
You can archive the folder as a .zip or .rar file and upload it to SwissTransfer, TransferNow or similar services and provide a download link to support @ incomedia.eu (without the spaces).
Thank you.

now it is converted but it crashes on the second page I edit, Eric, you have multiple copies of this project. I have no faith

and now I have to convert again. Fck. 

look at history, updates are not an improvement when it creates issues. I doubt your testing procedures. Very much

reality is, I can send copies but it never came back as  solved, and efficiency varies between 30 and 90%, 100% is when software runs without issue, today I am at 30%. FYI and like other times we sunk this deep, we the users have to find ways to work around the issue.

but Eric, I wish you a Happy Easter, and I am not cynical saying that :) only half drunk

Hello Raoul,
I have previous copies, send for issues unrelated to this as far as I remember, this is why I requested it.
Unfortunately, beyond not having encountered this during our testing, no other users have recently reportes this kind of issue, so it seems likely to be associated with your project specifically, for example.
I remain available.

ask AI :

Limitations in scalability and performance

Although the software advertises "unlimited pages," in practice, users report performance issues with larger projects:

Slowness on large sites: Very large projects (hundreds of pages) can make the software unstable or lead to extremely long loading times during editing and uploading.

Eric, appreciate you are responding. Fact is, sending files never solved a thing. It must be easy for your firm to have a bogus project of say 500 pages and side walk your  enhancements . and see what happens. Does not require a beta group. The beta group you ask to test when you have tested your own big projects, not the volenteers with windmills websites with 6 pages or so in the beta group. So do your thing, I will confirm you the result, and this week the result is a big negative. and you means the firm, not you

and if you cannot reproduce the error, tell us what hardware to use! Problem solved, not?

In the hope to protect myself, I labeled 150 pages as in development. Result when I edited 1 page: it renders all the pages, and uploads 160 pages instead of 1. While I try to learn the system I am only focused on 1, I get all to render. There is something wrong in the apprioach of "user experience". Invite, not me, the heavy users for a day in Milan, and we will tell you, or tap your fingers (not you, the firm) when you do not understand. This issue should not fly around for 10 years plus, this should be tackled once and for all times.... A matter of flying from the right angle towards the issue....

Alternative: get a big instutional, and prove to be institutional supplier, and charge me double

Alternative: get a big instutional, and prove to be institutional client, and charge me double

you get what I mean

Placing pages as  in development caused the rendering overload, at all stages, with all (small) tasks. FYI