Unable to open field properties #269
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#269
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Steps to reproduce the issue
Open JCB Admin -> Fields -> New field -> Select field form dropdown.
Expected result
Field properties to appear.
Actual result
Field properties does not appear, errors in the javascript console and web server log.
System information (as much as possible)
Additional comments
I can provide admin account if that will make it easier.
from nginx access log:
There is this id=24 at the end. If i remove it the query downloads a joomla.json file. If i don't it returns error 500.
@peterpetrov I have no idea why it does this, other then that it is related to NGINX.
I do not get these errors, ever... but I am on Apache. The JavaScript is simply making an ajax call to get content for the page.
You can see the code for those calls in a few places:
You tell me what am I doing wrong and I will fix it.
It doesn't happen on 2.7.2. Since 2.7.3 i am getting it.
will install apache later to confirm your theory.
Okay let me look at what changed in those areas from 2.7.2 to 2.7.5
Okay you will see that version 2.7.2 was completely removed from the history since it had to many bugs. So you get version 2.7.1 and then 2.7.4 and the whole fields area changes in that jump, from an xml field to a subform field that gets build with ajax. So major change in the hope of making JCB easier to use.
If you run Joomla in Docker and then install JCB v2.7.5 all works as expected.
In fact v2.7.5 was the first release to actually run out of the box in the Docker Image 😄
Previous versions had a bc function missing, so we added a wrapper. Just another question, have you tested the staging branch as it is almost ready for the release of v2.7.6
I fixed it finally. I am not in love with apache and i was close to go back to it but no :).
The problem was that i was missing php-xml (php72w-xml in my case) extension. Right after installation it worked. Apologies for the bells and whistles.
That is create news... so at least we know JCB runs on NGINX 👍
I know it runs. It is also faster compared to apache. I just needed to find what was wrong with it. Thanks for the patience :)