New versions 
Autore: Marius T.I wonder why new versions appear every year ...
Before the old version is stable and smooth, another one is released with its new problems.
I haven't updated my version since 16.3.1. because I don't see why. I have isntalled the new trial and all I can see is that the items are moved and got new colors. Why should I search for a new item every year? I don't.
Some certain problems have not been solved since version 12.
For example, exporting images: every change exports duplicates of images and it is a nightmare.
Moreover: if I change a single page it will create duplicates of images from other pages that must always be copied content from Files-Gallery-Images with the option "Skip All".
The result is a huge volume on the server. Errors that are not repaired from one version to another such as the fact that a certain image is not found on server although in preview and step 5 "check" can be seen.
In my case is the image of RSS that has been replaced with a text looking bad and again each export doubles the volume of data. It is the "RSS" text on footer in http://www.softedu.eu because no Png image could be displayed online.
Another issue: the settings of main menu can't be copied into Sticky bar. I made a post special for this but nothink changed. I attach the Png file and please note that the background is blue so the Png is on white. What is the problem with this Png attached? In the next post I will attach the youtube icon which also cannot be displayed online.
In fact I am wondering if ANY problem coming from users was ever solved. If yes - how many?
With all its problems it is the best web program I could found. It could be fantastic!
Autore
Second: the file in attach is another image can't be displayed. The Preview and CTRL+Preview shows that is ok. Not online. I have replaced it of course with another hundreds of duplicated images in Files-Gallery-Images folders.
Autore
3. The email button on the footer does not open a Thunderbird or webmail page. It can be found on the footer in http://www.softedu.eu and the code attached is ok.
You will release a new version soon isn'it it?
Quel bottone apre correttamente un programma di posta se hai in windows un programma predefinito installato e configurato... (thunderbird, Mail; Outlook...)
e difatti da me funziona cliccando il tuo pulsante nel footer
NON può aprire la Webmail !!!
Per quanto riguarda le immagini doppie/raddoppiate, credo che l'ultima versione , che è in BETA (la 2022.2) con la sua nuova gestione dei file risolva molti se non tutti di questi problemi...
Comunque lo STAFF, se interverrà ti saprà dire di più...
Autore
Bună Claudio. Puteți răspunde în EN, vă rog, deoarece traducerea este foarte proastă, ca să vă înțelegem? Ca de obicei.
Butonul de e-mail este problema mai mică. Le atasez pe cele vechi si mari.
Autore
Regarding duplicate images from the 3 folders assigned for export we have had this conversation from version 12 to 14 and now 16 ... it is unsolved today. If you remeber and we can search I have sent you the entire project. Still waiting a solution ...
The ideea of the first post was to solve the existing problems an then release a new version. Do we have an issue with this allegation? Because I can prove it - I already did it.
Will be kindly appreciated the answers to the other question like how many issues coming from users where solved?
Waiting for the new release ?
Forse non mi sono sbiegato bene ... ma NON faccio parte dello STAFF Incomedia...
Attendi lo STAFF e leggi il changelog
https://helpcenter.websitex5.com/en/w5/changelog
Ciao.
Hello Marius,
You are right. We are waiting since long long time some fixes not availabale today.
And users need to wait a new version with new functionnalities where the priority is done.
And if in this new version fixes are available, so it's a chance because like you explain Incomedia does not listen his customers. They prepare always news functionnalities (therer are welcome) but bug fixes is delayed... and it is never a priority.... Always.... Always..
They don't have a software developped to provide fixes very quickly by 1 or 2 DLL or other mecanism. Always they need to re-compile the complete softwareto provide fixes even just 1 fix.
Like it has been developped by many software companies, the Xpress-Update notion is not a vision to Incomedia.
By chance they don't provide an Anti-Virus solution where updates are daily !!!!! where all software is not reinstalled at each time.
So it is a choice from them to continue to work like this. Or probably more a R&D staff constraint
it's a pity.
Enjoy!
Axel
Marius, it would be wonderful if you could test your project with the latest beta release, so for this reason I have marked your post for attention by Incomedia. Perhaps they can grant you permission to play with the beta (although this is unlikely because you do not have an active license).
Looking at your provided screenshot I suspect the beta version will have little effect because each duplicate image appears to have a unique name. This is probably caused by the techniques you have used in the past (eg duplicate a gallery and this resulted in duplication of every image in the gallery with a new name). Having said this, I have loaded an old project where I know there were once many duplicates, I exported the website to a folder and can find very few duplicates. I may have rectified this in the dim dark past, or it could be a function of the new software.
I have not been able to recreate this problem in the beta with new projects.
I look forward to Incomedia's response to see if I am even close to being correct.
Autore
Hi Axel
Yes it;s a pity. They could gain the entire market. But not like this.
Hi Esahc
" This is probably caused by the techniques you have used in the past (eg duplicate a gallery and this resulted in duplication of every image in the gallery with a new name)".
Why should someone duplicate a gallery? Why duplicate all galleries because the duplicate shows everywhere!?
Why the Png attached above refuse to display? It is my fault too? Let's be serious ...
No, the problem was from the very beginning with version 12 and it's causing the same problems in version 16.3.1.
You can find old posts about it, I even sent the entire project to Incomedia and no solution.
That's why I have asked about tne new versions when the old ones are not reliable 100%. And we have some more questions in the first post.
Second: the testing with beta release colud not help at all. I expect ti work fine with actual version as it should be normal.
There are more problems but I take them one at a time. The next will be about code and W3C validation. Without me doing something the exported code is wrong due to W3C standards.
But let's wait maybe someone will answer (in English) to all questions above.
Kindly Regards, Esahc and Axel.
Absolutely full agree with you... their GUI is awesome, but their will is theirs and not that of the customers. And they are wrong.
Enjoy!
Axel
Autore
More about new version: I have installed the actual 2022 June version to try and see if the duplicate problem is solved. I have imported the old project made with 16 version into June 2022 Pro Version.
First I can read the warning about conversion to the new version. Which is normally.
Second: after the conversion was made we can read ... "the project it was made with a LATER version".
Unbelieveble!
Autore
Axel: I have asked about a way to copy the settings from the main menu to Sticky Bar, lon time ago.
I am curios if they have solved this at least. I bet no.
Marius, I believe there are severe limitations on the number of pages allowed in the trial versions, this may be the cause of erroneous error messages. The beta release has no such limitations, probably better to await incomedia. You speak of version 16 as if it was recent, sadly it was released circa 2015, much has changed in WX5 (sadly also much has not).
On the subject of sticky bar, I always assemble my menu bar and then copy it to the sticky bar (sadly component by componenet, but none the less, I copy it)
Always lost time for nothing...
At each time there are news issues, not explained... beta, preview, not really ready and so on...
Grrr....
No new version "stable or not" has been populated since 6 month at minimum... So no fix... Just Beta and Preview because Incomedia has decided "alone" to change many things into the software... and during this time, fixes are not distributed for customers... we are waiting again, again....
Axel!
And not enjoy this time .
Autore
Esahc, if "there are severe limitations on the number of pages allowed in the trial versions" this is not the message I colud read. O could read that nonsense with later versions.
Regarding the old version" I am not speaking about it as if it was recent" but I am speaking about it as it should work.
I do not have expectation about changes in new versions. Like always. I won't spend another 100-200 euro to find that.
Don't have expectation about Incomedia too: the forum is full with problems and they simply don't care.
Hello Marius
I'm sorry to hear such a harsh review of the latest version, especially when it is supposed to fix exactly the issue you're so vocally commenting about.
The trial or demo versions cannot import older projects, so you won't be able to edit your project in the trial version to test it out
You can, however, proceed in two ways:
1_ Test this out with a new trial project (which might however not be ideal and I see why)
2_ Purchase the newest version, make a copy of the project and test it out. You have 30 days time to see if it suits your needs or not. If not, you can get a full refund and keep on working with your version, so no loss at all. Should it provide to be a step forward to you, you can then keep it
Please let me know if this seems reasonable enough to you
Thank you
Stefano
full agree
@Marius - Don't have expectation about Incomedia too: the forum is full with problems and they simply don't care.
About this matter specifically, I would just like to clarify that the Help Center is the main hub for technical support.
For this reason, it is clear that most topics will about about issues or stuff that needs to be verified or fixed. This is a technical support forum, which is made exactly to get reports of issues. It would be weird if the support forum was void of any kind of report or issue
Thank you
Stefano
@Marius,
Since long time now, I have stopped to test Beta or preview. We spend our time and it is not our job to the Incomedia quality departement. !!!!
And to finish when the new version wil be ready, new issues will be discovered on old ready functionnalities...
Enjoy!
Axel
@Stefano,
Like you said Stefano, many issues are here discovered by users and are waiting of fixes.... since mays weeks, months and also many years .......
It is a good reason why this forum is not empty... !!!!!
Enjoy!
Axel
Agree with Axel / Marius T. 100 %...
Too good a product with the wrong vision of further business ... I don't understand why you don't reward or stimulate old customers with loans or something ... You have us as free debuggers and I think we do the job very well for you ... Or I'm wrong ...
Hello X5
Just posted in same idea...
https://helpcenter.websitex5.com/it/post/251407
Autore
Hi Stefano
1. What exactly does "vocally" means for you, coming from a client? "Harsh comment" maybe and it is deserved but "vocally" ... ?
2. It would be wonderful if the support forum was empty. But is not. I ask again: how many problems that users (free testers and enthusiast bug reporters) raised did Incomedia fixed? Which?
Because I started to look more careful at details: for http://www.softedu.eu here is the result of W3C Validation which is a standard: https://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.softedu.eu%2F
W3C validation is the process of checking a website's code to determine if it follows the formatting standards. If you fail to validate your website's pages based on W3C standards, your website will most likely suffer from errors or poor traffic owing to poor formatting and readability.
I "vocally" ask you why one can find here in the code that X5 generate issues like this:
- Element style not allowed as child of element div in this context
- The type attribute for the style element is not needed and should be omitted
- The type attribute is unnecessary for JavaScript resources
Does "new version" solve thise bugs?
3. I have already purchased 3 versions and I am expecting to work properly at least the last one. I have no intention to buy another bunch of problems and bugs while the old ones are unsolved.
So it is reasonable for me that the paid version to work and the reported problems to be fixed BEFORE you move to a new version.
I expect you to release updates in order to fix the bugs even for EARLIER versions of course. So thanks, but no.
So I believe I have found the answer: you release new version every year to avoid fixing the current one. Vocally enough?
Autore
Oh, and the plugins that are available only for the current version, this is really to much. You have this topic also on the forum. This is the reason for I never took plugins with credits.
In fact there are plenty of topics there on forum and also plenty of vocal questions right here in this topic. Answering to one of them and ignoring the others does it mean lack of time or is a technique? Because there are many left unanswered.
Ok. It is your business. I have my web program working for life even if the company goes bankrupt, I can live with its problems but no more money will be spent until honest behavior towards customers.
BTW what happens to the activation of licenses for life when the company goes bankrupt? Which I hope won't happen of course.
Thank you too.
Autore
Yes you all are making a great free job. Too bad it's not followed by bugs and problems solving.
Hello Marius
I will try to address all of your questions and doubts in the best way possible, since this is what matters the most to me and most certainly to you too:
1_ By "Vocally" in this case I meant that in your current topic, the malfunction you mentioned the most refers to the persistence of unused files. Since this was the main issue you mentioned multiple times in the topic, I found it fitting to let you know that the newest version aims to fix this specifically
2_ Since we actually keep track of all reports and fixes, I can safely say hundreds. Of course, the perception of this can change drastically between users according to whether the issue you presented was every fixed (either quickly, slowly or at all). As I'm sure you understand, not all fixes take the same time to be implemented. In some cases, major reworks are necessary which requires long planning to make sure they're made the best way possible.
Of course, should there be any outstanding bug that was never solved yet, I always encourage you to open up a new topic about it. I will be glad to check the situation for you.
About the issue you mention specifically "Does "new version" solve thise bugs?" I can guarantee that several such instances were solved version after version. I cannot tell for sure about your instance specifically, but I would be more than welcome to try that out for you with your project if you wish, or you could try that yourself by purchasing the software temporarily just for testing as I mentioned before
3_ Unfortunately, this is simply not possible. Not every bug for every older version can be fixed indefinitely. This is so for every software or service out there. Older version will always have the chance of presenting errors that weren't solved in time or perhaps require too much or a rework to even think of updating it. It is normal that some fixes can only come with major rework or changes that only new versions bring.
In this case, I can only advise keeping up with updates in order to make sure that all issues are taken care of as well as new features. There is no point in me telling otherwise when this simply won't be done. If you wish to solve some of the old issues that are still there in v16, you will need to update the software
Again, I am always available to clarify any doubts or questions you might have, if possible. I will not discuss the number of bugs we claim to have fixed or that the community claims we intentionally ignored because there would simply be no end to the discussion.
As far as I am concerned, if a topic with an issue is opened, I will always attempt to do my best to verify it and make sure that it can be dealt with in the best way possible according to our possibilities, even though admittedly, the solution or conclusion that comes might not always be the best-expected one
Thank you
Stefano
Autore
Hi Stefano
1. “Not every bug for every older version can be fixed indefinitely “. Well this is exactly the point: at least major bugs should be fixed definitely right on time for that version at the moment they are known, before realising the new one. Otherwise it means that the software is not complete when its license and updates expires.
2. Maybe some of errors where fixed. I have noticed only one, the one in which user raised attention about sub-level menu not shown and only there I could notice a fast answer about solving it.
3. Take your time please to look about the export code issue section about W3C validation in previous messages above.
4. Regarding duplicate files: I have tested a new site with 8 images in a gallery. Looking at first export we have 16 images: 8 pictures and 8 thumbnails. I i thought that the thumbs frame is made by code and one can see in fact the same picture once in full size and once in thumb size.
Well … one of the problems are here! When only changing the gallery style we obtain 26 images because … there are 2 pairs of thumbnails. So the X5 does export the thumb as image by itself. At the second style change (3 rows for example instead of 2 but with the same gallery style and again no image changed inside gallery) I get 32 images.
Seems for me hard to understand the random naming of exported images instead preserving their original names. In that manner the duplicates should not be possible. Instead we get "1_thumb_ha4bw7wg". I am not qualified to judge if the SEO is affected too.
I have uninstalled the trial but you may easily test with a few images and changing gallery style.
This is for the test page.
Inside the one I am working I got 120 pages and hundreds maybe thousand of images in a 500 Mb project.
If I change only one page WITHOUT images inside I get duplicates randomly for the other pages.
If I change only one page WITH images inside I get duplicates on that certain page AND randomly for the others.
If I change a page with images the X5 export will duplicate images from other pages.
To be clear: when uploading in Total Commander and pressing F5 I choose “Skip” on those 3 folders Files, Images, Gallery so only the new ones will be uploaded.
Doing this I can see an important number of (“new”) pictures to be uploaded at a minor change in only one page sometime only regarding the text.
More: there are some images that simply can't be uploded. I have attached above in one of the answers an RSS icon which refuse to be shown online. The preview inside X5 looks fine. Finally I have replaced the icon with text.
Briefly I must browse every section and page to see if I get images offline (when you see only the alt tag). But when preview inside X5 everything looks fine.
5. Generally I do not change versions of progams which is working simply for the reason I do not want to dig for the places where new items are moved. Adobe and Autodesk got the good habit not to change menus and tools and not to move them. Of course the new one is in the new place but the old ones are in the old places.
6. The most important reason I do not update is that we had this conversation about a previous version. I have updated and nothing changed. The only change was that I had to spent hours to discover the new GUI.
Kindly Regards.
Autore
Edit: I can see that he naming of images is correct in the X6 16.3.1 version, at least for this test. But my project was imported from version 12. Maybe version 12 is guilty for the crazy naming. But why vers 16 does not fix this?
It's absolutely impossible and unimaginable to rebuild the whole project with version 16, I think we agree about it.
Autore
Another example form 10 minutes ago: I have modifyed a page by deleting one youtube video incorporated.
No touch in images. No changes in galerry.
After upload the update shows this - see attached.
So again F5-Skip all images. Now I will spend one hour to see if i got missing images in other files.
Marius, the version that (hopefully) fixes this issue is v2022.2.2beta, not v2022.1
If you can advise how to construct this page I will try recreate the problem in the beta version if requested, I am sure Stefano would offer to do the same.
Autore
Thank you Esahc for your valuable help. I don't want to migrate to a new version because I do not trust the company anymore. This problem maybe will be solved but I am pretty sure that pther problems will appear and I don't want to waste time anymore.
I will subscribe again when every version will be debugged in time.
Autore
Dear Esahc, since you are the only one responding from the team, I copy here a message from above:
Because I started to look more careful at details: for http://www.softedu.eu here is the result of W3C Validation which is a standard: https://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.softedu.eu%2F
W3C validation is the process of checking a website's code to determine if it follows the formatting standards. If you fail to validate your website's pages based on W3C standards, your website will most likely suffer from errors or poor traffic owing to poor formatting and readability.
Why one can find here in the code that X5 generate issues like this:
- Element style not allowed as child of element div in this context
- The type attribute for the style element is not needed and should be omitted
- The type attribute is unnecessary for JavaScript resources
I think we must all accept that INCOMEDIA makes and sell a product (X5) and we buy and use the product.
The strategy for what is made in the product is all up to the seller.
We decide if we will buy the product. And if we will upgrade the product.
If we find that we don't get enough for our money we can stop buying and find a new store.
This is how it functions for most products. We users can give feedback to what functions we would like to see in the product. If it will ever be made is up to INCOMEDIA. When we feel that too many things that WE find important will never be made, we can make the job with another product. I think there are more users that use different tools for different jobs.
I will keep a product as long as I find it gives value for the money.
I have made several idea-posts for using a database for products - as long as this is not made I cannot use X5 for an e-shop. But I can use it to quicly develop a website, even if it produces much more code than should be needed.
The idea posts is for suggestions of new things.
The "standard" (Question) posts is for reporting errors and for asking for help for a specific problem.
I think we could need some new kind of post on this forum:
- Discussions on how to make the X5 a better product and user feedback for the X5.
I would like the "normal" posts to be posts about one single problem, where other users could give what they think is helpful suggestions how to "solve" the problem, or the X5-staff should give response if it is a bug-report that more users report they have also discovered. I will now make an idea post for a new type of post
Marius, I am but a moderator. . . .
As for your concerns over WC3 validation, I do not see these as critical. I do see that it is important that Incomedia is aware or or made aware of inconsistencies and faults so they can continue to improve their generated code as they have done in the past.
I took interest in your post because I too have had to deal with duplicate and redundant images in the past, and I have always stuggled to offer a succinct answer when trying to assist other users with this issue, this is why I offered to attempt to recreate the problem you described. Incomedia has made changes in the past that seem to minimise this problem, but with 2022.2 they have made a concerted effort to overhaul the underlying file system to minimise this duplication problem and perhaps more importantly provide a path for users to rectify and delete legacy and redundant images locked inside a project.
If you wait until all bugs are resolved and all functionality that you desire is incorporated into WX5 then I am afraid you will still be using V16 when web standards mean it will no longer be an acceptable platform. What version Windows do you use? Do you hold Microsoft to the same high standards? I know if I did I would probably still be using MSDOS 3.3 :-)
Autore
Well I see the fact that the exported code is not conform with standards as a serious problem. Try now with beta and validate export on w3c, you will see.
The issue was noticed some time ago when my version should export the right code.
No, I am using MS Dos 3.4 of course and old Commodore.
The problem of updating is way more complicated and it should be done with proper judgement.
this is not the issue here but it is the fact that we have several incomplete realeses.
With unsolved problems.
Autore
Hi Esahc,
Some years in IT and graphics learned me that if something works you simply do not update it, instead if you want to play with and learn. If the computer (my Commodore which I am using with MS DOS) is it really a working tool you're careful with updates or at least you can read about them - see KB's and rollovers on updates and so on.
A brief example found in 30 seconds - I didn't really start the deep searching.
Here we have a very attractive webpage made with Incomedia WebSite X5 Pro 2022.1.6:
https://www.alexandre-peronny.fr/
You can see that the design is amazing. Let's look at the code.
You can see that the code exported by the last version can't be also validated and this is it at a very first glance:
Warning: The type attribute for the style element is not needed and should be omitted.
From line 31, column 3; to line 31, column 25
int" />↩<style type="text/css">#plugi
Warning: The type attribute for the style element is not needed and should be omitted.
From line 32, column 3; to line 32, column 25
/style>↩<style type="text/css">#plugi
Warning: The type attribute for the style element is not needed and should be omitted.
From line 33, column 3; to line 33, column 25
/style>↩<style type="text/css">#plugi
If it was a user mistake I bet that I can find more.So, in brief I believe that everyone made his own point: the Incomedia Team will continue to release a new version every year without resolving the bugs of the current one and some users are happy but others are not.
I am among those who are not satisfied. Incomedia allows us to publicly display disappointment, which was to be expected.
Let the topic be opened :-)
Marius, these are warnings, not fatal flaws.
This could be a sample site to demonstrate WX5 optional objects, but even if created by Incomedia I would be most concerned with the slow loading times (at least it was painfully slow to load pages down here is Aus). First thing I would do is run this project through step 5 optimisation options to hopefully reduce file and image load times.
I shan't comment further . . . have a great day
@Marius, all
Just to confort you or not !!! Today June the 24th 3.30am....!!!! No replies from Incomedia on FR and US forum...and probably not anymore into other language.
Does it normal to have absolutely no answer from the company when we paid Update protection to have fixes and support.
The support does not be done by other users, but by the editor company it seems !!!
It is my personal conclusion
Enjoy!
Axel
3:30pm !
Axel, why the concern?
I see nothing to respond to in this post. There are no questions, just accusations.
Autore
Dear Esahc
Even if it is a demo page (which is not) even if it loads hard (which is not) it has absolutely no importance :-)
The subject is the code with errors exported by the latest version. Errors or warnings - that matters less since we expect a totally correct code.
And yes, it's obvious that the page is made with the X5 because it writes in the first lines, let's get serious =))
It has nothing to do with the size of the images, but absolutely none. In fact, the problem of the wrong code is signaled by Jacques entru version 2021.2 but also by other customers.
As for the "accusations", when they come from a dissatisfied client, urgent answers and ACTIONS are required. That's why they're actually questions or at least it demands answers and actions! It is easy to understand.
Once again I showed (as other unhappy customers say) that updates come with new errors. While the current version is not finalized, a new version is published. Errors on customers' money.
Have a nice evening too.
Hello Marius
You are definitely right in what you're mentioning in your latest topic.
Of course, just like Esahc said, warnings are indeed less "penalizing" or dangerous for your website, but we are interested in fixing those just the same.
However, the only for me to be able to do this correctly is by asking you to send over a copy of the project where this happens, or eventually, also let me know exactly how to get that result so that I might reproduce it.
By doing so, I will be able to report this to the developers.
Keep in mind that the code gets updated constantly, as new functionalities are added and updated. As we fix some situations, it is of course possible that new ones appear, considering the huge amount of combinations and settings you can get out of the software.
Just let us know where the issue is and I will personally report that for you
However, please do so on a new topic, private or public if you do not mind eventually sharing the project for analysis publicly. I will handle it there since this topic is not suitable for continuing a proper testing
I remain available here
Stefano
Autore
Hello Stefano
Yes indeed there are not major issues there in the code. Regarding my project there is no sense to be sent because is made with 16 version which is dead and there are even mistakes made by myself, like open H1 tags and open <hr> element and so on.
The project I have speaking about is made by a user and the link to the project is inside the message abeove but I do not have the iwzip project: https://www.alexandre-peronny.fr/
About refrehsing the code: there are no changes in Html 5 and CSS 3 in the last years. So when a new feature is added of course there will be a new code associate with. But the code of the old style elements should be the same.
I really appreciate the team's attention for problems in X5, in fact that was part of my original complain in the first topic.
Have a nice evening and thank you for your attention in the topic.