Administrator schrieb: Hi Nikos,
first of all.
I'm sorry for your trouble and the time you have spent to solve the problems and I thank you for posting your problem and the solutions here!!
Actually Visforms 3.5.8 and 3.6.10 are both compatible with Joomla! 3.4.8. Visforms 3.6 was my beta version with lots of new features for a long time and I made it a stable version just last week.
In the download manager I naturally provide this latest release (3.6.10), which now is the latest stable release as Version for Joomla! 3.4.8 but Visforms 3.5.8 should work with Joomla 3.4.8 as well.
The reason why I did not enable the update notice for Visforms 3.6.10 in administration is, that it's new features sometimes require changes in the view files. So if people have created template overrides they may need to redo there overrides after an update to 3.6.10. I do not like the idea of people updating Visforms only because there is an update notice in the administration, if they do not really need the new version. But I want people to update because they need one of the new features. If you have a new installation, template overrides are no problem.
While pondering on what to do about that, I simply did not launch the update notice.yet But I can understand that this is confusing!
Your problems with the forms are a result of the Joomla! update which seems to happen on some installations but not all.
Is it possible, that you display the forms with loadposition inside an article?
Yes and I think this specific problem was solved with Visforms 3.6.10.
Kind Regards,
Aicha
Hello there,
Thanks for your answer 1st of all !
I understand your answer.....The only i say that this did not happen in one joomla installation but it happened as i said in 10 sites.... I just upgraded joomla and your compoment and after that none of my forms were working... until i uprgaded to 3.6.x
I have never had any other issue with other compements like this .....
Your component is really good but if you keep doing this with the upgrades ...i will be forced in the future to change component... Simple as this !
Thanks
Nikos