After updating to Joomla 4.2.2 Error 500

[Mike J]

Hello Niosme,

Well, you seem to have a good head on your shoulders which is a good thing.

Was just thinking back to Mambo which in time forked into Joomla and MiaCMS.

Why a fork? They felt that the policies, processes, and priorities of the official Mambo Foundation were having a negative impact on the code and the community.

Funny how things morph over time hey?

[jflash]

Joomla 4.2.3 and VM 4.0.7.10717 - Custon Fields work again, i can open them and save them without error 500 (Y) Thank you!

[Mike J]

Great stuff jflash,

Thanks for that.

Are you able to take live orders successfully on Joomla 4.2.3 and VM 4.0.7.10717?

It's been a while since I've tried VM on J4.

Many thanks again.

[Milbo]

All the situation is tragic. Hazael stop acting like a clown.
We post here bugs and fixes and they never get fixed like those.

https://forum.virtuemart.net/index.php?topic=148808.0
https://forum.virtuemart.net/index.php?topic=148809.0

We want to help Milbo fix the component but he seems he have not the passion and strength to continue developing this project.
I started figuring out that developing a new open-source eshop with all virtuemart feautures for joomla is the solution. I am so close to start this project instead trying and dont know what problem i will face with this kinda abandoned component in each update.

You did not answer one of the threads. The other right solution is already in the new core vm4.0.7.10717, and just a hint I was in summer holidays. If you want the help the project, test or provide code. If you provide code, it wont take long and you will be invited in the dev chat, which is faster then the forum. Also good testers get invited. or nice explaineres, helpers, etc.
But you have 19 posts.

and for all the people who say, that vm4 was not ready. It was completly ready for Joomla 3! We cannot be ready for joomla 4, because it is not stable. One very simple example is the payment/shipment/custom edit view. They added in a common subfunction ( I think getProperties) the ability to work with arrays. Our shipment/payment/custom keeps the "read form" as form. Using getProperties kicked the loop.

And the ultimate evidence is the name of this thread. "After updating to Joomla 4.2.2 Error 500".

That was all the time that way, the whole year. We had the stuff running, suddenly it stopped working. We tested it in january and 1-2 months later it was broken. If you view from the j3,php 8.0 viewpoint, VM4.0.7 is very stable, or better said matured. But Joomla 4 and/or PHP8.1 makes problems. Not php8.0 btw, that works imho well already.

[Milbo]

Great stuff jflash,

Thanks for that.

That he tested it? It was me who invested the two hours, just a little hint. I spent the last 2 weeks 50 hours at least for core development.

[Milbo]

The search is imho the last problem.

What a foo. Long time ago, I wrote it so, that vm encoded the strings to html entities. I removed that 1-2 years ago, because some people had trouble with imports.

now joomla changed the db handler (and it looks like for j3 also) that any query gets encoded. So they adapted my "stubborn" way for which I got so much negative response. But yes it is just a lot more secure.

Btw the search should be also fixed.

[Milbo]

Did you ever test 4.0.6 (stable, compatible J4), 4.0.4 (stable, compatible J4) & 4.0.2 (stable, compatible J4)?

Yes, I have tested all VM versions starting on January 20, 2005. I create new pages regularly and update old ones. Currently I'm working with Joomla 3 and 4.
I have a private dedicated server where I test various PHP SQL system solutions etc. Until then, I regularly report critical Virtuemart bugs. When they are not repaired, I waiting patiently for a new, improved version or (if necessary) I solve the problem myself and I don't cry as much as some. I am not writing to anyone privately (like some): "request to fix my Virtuemart"[LOL]

Thank you for your nice words in this posts. Just some notes here. I hope you post your fix.. And it is allowed to bump a post, but not more than 1-2 times a week.

I think a professional bug reporting application would be a better solution than this forum.

We have that. But it is not so easy to maintain. We just get not used to it. Stephan tried. Just use this https://dev.virtuemart.net/projects/virtuemart/issues login/create an account. I think posting tickets should work without any special rights, if not, we can change it.
But we need a mod or many mods there. There is a problem.

[Darko F.]

We have that. But it is not so easy to maintain. We just get not used to it. Stephan tried. Just use this https://dev.virtuemart.net/projects/virtuemart/issues login/create an account. I think posting tickets should work without any special rights, if not, we can change it.
But we need a mod or many mods there. There is a problem.

How to register dev.virtuemart.net I didn't find,  I like to post bugs, have few shops using VirtueMart for free and I would contribute with testing just to help. Is no problem to post on the forum, but is problem to know if somebody already posted the same bug or not. So probably we just repeat the same bugs in 20 different topic .

[StefanSTS]

[ like to post bugs ... Is no problem to post on the forum, but is problem to know if somebody already posted the same bug or not. So probably we just repeat the same bugs in 20 different topic .

I tried to revive the bug tracker, but it's not really used.
Important issues find their way from the forum into dev chat and are mostly solved quickly.

If issues are not solved immediately via the forum, the topic can be bumped.

What helps most, is a good description of the isssues and possibly a suggestion how to solve it.

The bug tracker has the same issue that bugs could be reported repeatedly, same same like the forum.
In the end the forum is the best place to report bugs, because everyone is used to it.

Stefan

[Mike J]

and for all the people who say, that vm4 was not ready. It was completly ready for Joomla 3! We cannot be ready for joomla 4, because it is not stable. One very simple example is the payment/shipment/custom edit view. They added in a common subfunction ( I think getProperties) the ability to work with arrays. Our shipment/payment/custom keeps the "read form" as form. Using getProperties kicked the loop.

Thanks for the clarification Max,

RE: "It was completly ready for Joomla 3! We cannot be ready for joomla 4, because it is not stable." We are in complete agreement on this which is great.

As this is true, I believe that VM 4.0.4 (stable, compatible J3/J4) & 4.0.6 (stable, compatible J3/J4) should never have been presented as J4 stable at dev.virtuemart.net back in July - present.

It would have been extremely helpful for many of us to have read the comments you make now back in July (Would you consider changing the erroneous files names at the dev site to read: VM 4.0.4 (stable, compatible J3) & 4.0.6 (stable, compatible J3))?

A lot of us spent weeks going around in circles on J4 because we thought the problem was at our end. If you had communicated this to us back then it would have saved many of us massive headaches (I've brought templates that only work on J4 and things like that).

RE: "That he tested it? It was me who invested the two hours, just a little hint. I spent the last 2 weeks 50 hours at least for core development." Good on you for fixing that. A big job I know and you're doing great. Nice stuff!!!

Unfortunately, I haven't heard back from jflash. I thanked him for letting us know that progress has been made because sometimes communication around here is not the best but sadly, he never responded to me on the other, more important part of my post, "Are you able to take live orders successfully on Joomla 4.2.3 and VM 4.0.7.10717?"

[Milbo]

The problem is that the it worked in j4 and then it suddenly did not work. It was also communicated in the news. For example here https://virtuemart.net/news/506-virtuemart-4
"We originally had planned to release this on Christmas, but it was not possible to keep the date due to many changes applied to joomla 4 after it's initial release."

I only write this, when I am sure that it worked before, that means someone tested it on boths versions. Or here https://virtuemart.net/news/507-bugfix-release-4-0-4

"VirtueMart 4.0.4 contains various bug fixes and improvements. Especially it solves some problems reported to us after the release of the previous version of VirtueMart when it is used along with Joomla 4.1.x."
j4.1, not j4.0. Of course it worked not perfect on the first release for j4. We also mentioned that in the news and in the forum quite often.

"We still have to iron out a few minor complications with it, but it already works for a number of early adopters.."
But it was some minors and got more and more. So as the news said, we had more than 20 people already working on it and said "it works, but the routing is still a mess, but works", the more and more stuff came up.

[Mike J]

Thanks so much for responding here Max. I know you're a busy man, so I do really appreciate you taking the time to respond.

https://virtuemart.net/news/506-virtuemart-4 was published on 29 April 2022, so well before the following Virtuemart releases were promoted as being J4 stable:

4.0.2 (stable, compatible J3/J4) 13 May
I found that the admin State Drop Down error made this version totally unusable on J4. This was confirmed by GJC Web Design as seen here: https://forum.virtuemart.net/index.php?topic=148440.msg529470#msg529470

4.0.4 (stable, compatible J3/J4) 5 July
I ran into real problems here which I reported: https://forum.virtuemart.net/index.php?topic=148569.msg530043#msg530043

4.0.6 (stable, compatible J3/J4) 7 July
July 9, https://forum.virtuemart.net/index.php?topic=148576.msg530064#msg530064
On July 10, Sharing my experiences with Joomla 4.1.5 & VirtueMart 4.0.6 10690 https://forum.virtuemart.net/index.php?topic=148403.msg530008#msg530008
July 11, https://forum.virtuemart.net/index.php?topic=148569.msg530014#msg530014      
Notice what ssc3 commented here: https://forum.virtuemart.net/index.php?topic=148609.msg530754#msg530754 "The issues with VM 4.0.6 were actually found on the day of its release. At the moment VM 4.0.6 is labelled "Stable" and on the Admin download,  but has a critical issue which will break a store."

When you say, "it worked in j4 and then it suddenly did not work." I never got any of these VM versions working on J4 and I tried close to all 3 release dates. I did not find that there were 3 consecutive Joomla update releases that could have quickly broken each of these VM updates consecutively.

The closest you got to revealing the seriousness of the J4 issues was on 5 July before 4.0.6 (stable, compatible J3/J4) was released.
https://virtuemart.net/news/507-bugfix-release-4-0-4 "it solves some problems reported to us after the release of the previous version of VirtueMart when it is used along with Joomla 4.1.x." This does not sound like anything serious, just minor bug fixes. What I am referring to are serious issues that made each of these VMs versions unable to take live orders on J4 – A very, very serious issue indeed.

Again I say, VM 4.0.4 (stable, compatible J3/J4) & 4.0.6 (stable, compatible J3/J4) should never have been presented as J4 stable at dev.virtuemart.net back in July - present.   
Would you consider changing the erroneous files names at the dev site to read: VM 4.0.4 (stable, compatible J3) & 4.0.6 (stable, compatible J3))? And, Would you consider changing the erroneous files names at the dev site to read: VM 4.0.4 (stable, compatible J3) & 4.0.6 (stable, compatible J3))?

I am a big VM fan but I am concerned that the reputation and reliability of VM has been damaged over the last few months as also shared by ssc3 here: https://forum.virtuemart.net/index.php?topic=148609.msg530754#msg530754
"It's not helping with Virtuemart's reputation for reliability."   

Again, I thank you for taking the time to share here Max. You've got a lot on your plate and I do thank for all that you have done and continue to do for the success of this shopping cart.

[hazael]

When you say, "it worked in j4 and then it suddenly did not work."

Unfortunately, this is the fate of application. Usually, any modification may adversely affect the performance of other parts of the application. The app developer may not know this. Therefore, for such an application, system, or website to work well, testers are needed to detect and report bugs to the developer

[Mike J]

When you say, "it worked in j4 and then it suddenly did not work."

Unfortunately, this is the fate of application. Usually, any modification may adversely affect the performance of other parts of the application. The app developer may not know this. Therefore, for such an application, system, or website to work well, testers are needed to detect and report bugs to the developer

Hazael,

I did not find that there were 3 consecutive Joomla update releases that could have quickly broken each of these VM updates consecutively.

If I were to say this is blue, you'll just come back say it's yellow. Big fancy words, but you're still in total denial.

You don't care what's true... You just want to have the last say and always be right. Your thought process is, "Don't confuse me with fact.... My mind is made up." 

Bottom line is:

4.0.2 (stable, compatible J3/J4) 13 May
4.0.4 (stable, compatible J3/J4) 5 July
4.0.6 (stable, compatible J3/J4) 7 July

... In the context of J4 are false promotions - They never were J4 stable.

You know it, I know it, everyone knows it but you still choose to defend the indefensible (for brownie points I guess).

"fate of application. Usually, any modification may adversely affect the performance of other parts of the application." This is ridiculous!

"testers are needed to detect and report bugs to the developer" Correct, but this needs to be done before each release is marked as stable. The very fact that I have to mention this here is bizarre.

Very sad, disappointing and your mindset is and will be very detrimental to the future of VM.

Again I say, VM 4.0.4 (stable, compatible J3/J4) & 4.0.6 (stable, compatible J3/J4) should never have been presented as J4 stable at dev.virtuemart.net back in July - present.
Would you consider changing the erroneous files names at the dev site to read: VM 4.0.4 (stable, compatible J3) & 4.0.6 (stable, compatible J3))?

[hazael]

Another beating of foam...
The moderator of forum should set up a new section: "Regrets & Sorrows"

your mindset is and will be very detrimental to the future of VM

You flatter me. My mind has such super powers? Am I a super hero?