search

JoomGalleryfriends / JG4-dev

Development repository for JoomGallery v4.x
GNU General Public License v3.0
10 stars 6 forks source link

Error opening Image Form View from the frontend #192

Open patafiole opened 5 months ago

patafiole commented 5 months ago

I have been trying to evaluate the status of JG-4 using the Github code such as it was on 2 February (ten days ago). The display of categories seems to work fine. But when I try open the menu link of type "Image form view" I put in the Main Menu I get the following diagnostic : COM_JOOMGALLERY_SERVICE_ERROR_LOAD_CONFIG 500 JLIB_APPLICATION_ERROR_NOT_EXIST JLIB_APPLICATION_ERROR_NOT_EXIST

The full error stack is to be found in the appended file. erreur_JG4.txt

Elfangor93 commented 5 months ago

@patafiole Can you please tell us your system information (joomla version, php version, db version, ...)

patafiole commented 5 months ago

Here it is : Ubuntu 22.04 with Joomla 4.4.2 PHP 8.1.27 MySQL 8.0.36 Apache 2 .4.58

patafiole commented 5 months ago

There are complications. The bug vanished from my site . However I managed to make it reappear as follows.

  1. Go to a site where Joomgallery has never been installed
  2. Install JG 4
  3. Create a menu item in your frontend menu with type link "List of categories" (just to be able to verify what you do)
  4. In the backend do components/Joomgallery/images/new to upload an image.
  5. Create a menu item in the fontend with the link type "Image Form View"
  6. Click this link, the error is there ! To make it disappear again do the following.
  7. In the backend upload a new image with title and description.
  8. On the frontend click again the item for image upload. The bug has disappeared BUT the form displays the values of the attributes of the image you just uploaded from the backend (title and description)
  9. Disconnect and reconnect to the site. This time you get a clean form with empty fields.

To me this suggests that there could perhaps be a piece of software somewhere being used by the image form views both in the front and in the back that would be mishandling the image ids and/or the UserState.

Now that I have been able to look at the frontend image form I found problems with it, but I am going to open a new issue for that.