Forum Replies Created
-
Posts
-
@JFS. Thanks for posting. I got your email. I just released version 2.0.1, which should fix the error you reported. I will update the JED listing soon. So, please update and Let me know if it is working now.
@Crazy5650. Thanks for sharing your experience and insight. I plan to revisit how profiles and short code interact together in an upcoming release.
In the past, the profile would always be the default unless you change it, and the shortcode only created local changes that do not reflect in the profile. Going forward, I want to make the shortcode actually alter the profile directly. So, every shortcode relates to a specific profile, but only if the folder location is the same.
To be honest, I have to review my own code to see what I have right now. It’s been a little while since I touched that part of the code, and I have worked on other things since then. Anyways, you can always go to a profile and click the “Save as Copy” to get a duplicate of a custom listing. However, your suggestion has given me something to think about.
@Crazy5650. Ok. Let’s leave it at that for now. If anything else pops up, just let me know. Best Regards.
@Crazy5650. Thanks for posting your error stack. I am not able to reproduce this error on my test systems. I have a fresh Joomla 4.2.5 installed, and installed the latest release of the extension. Then I added the shortcode {easyfolderlistingpro profile=”1″ folder=”images” method=”table”} then clicked Save, and I get no error. The article saved without any issue.
Can you explain what you are doing (such as the exact shortcode you use), so we can synchronize our actions, and see if I can reproduce this? Could you also update your Joomla version to the latest 4.2.5 instead of 4.2.3, so we can have equal footing for a comparison? Thanks.
So, as far as I can tell, there is nothing in the code that should trigger such an error. The error says that an empty string (”) is an incorrect value for datetime checked_out_time column. However, I don’t actually try to change or update the checked_out_time field in my code. This is done automatically in the Joomla code.
The thing is that when you save the article it renders the code, which executes the profile update to the database, based on the attributes in the shortcode. This is why you get a possible error when you save. So, any errors or notices will pop up when saving the article and not only when displaying in the front end.
@Crazy5650. Yes. I am glad the default is NULL. It is supposed to be NULL by default. The error you experienced occurs because of the invalid value “0000-00-00 00:00:00” being inputted into the field. I dealt with this issue since version 3.6, when MySQL deprecated the use of that value. I am not too sure how those values got into your table. There shouldn’t be anything in the code that does that.
Did you recently upgraded your MySQL from an older version to a newer one? Or maybe updated the extension from an older version?
@Crazy5650. Thanks for posting the version information. Everything seems fine. The only main difference between your setup and mine is that your mysql server is version 8.0.30, while my test servers use 5.7.34. Since your setup is on local development, can you check the the database tables, __eflp_profiles and __eflp_icons for what the default value for the ‘checked_out_time’ column is. It should be NULL. Whatever it is, please let me know.
If I could reproduce your issue on my test servers, that would be useful.
@Crazy5650. Thanks for posting.
OK. I am not getting that error on my test servers. So, something is going on with your setup. Can you please let me know your PHP version, MySql or Postgresql version, and the version of Easy Folder Listing Pro you have installed? Can you confirm that your Joomla version is 4.2.4?
@RichardXWH. There are different ways to use the “Content – Load Modules” plugin that is builtin to Joomla 4. One way is to specify a position. So, you have to create a fictitious position in the module, and then say {loadposition my_fake_position}. Another way is to use the module ID, and type {loadmoduleid 232}, where 232 would be the id for an Easy Folder Listing module instance. Another way is to specify the module name, with the title and style as optional arguments: {loadmodule mod_easyfolderlisting, “My Title”, my_style}
I don’t know anything about {module title=”Files”} relating to displaying modules.
@RichardXWH. Thanks for your question. Yes, the module can be used in multiple articles with different upload folders. Just create a module instance for each article as needed.
@serge73. Thanks for your request. I don’t usually do custom changes to my extensions. I don’t really have the time to do that, and I am busy with several ongoing projects.
@serge73. Thanks for posting. Sorry for not replying sooner.
I currently can’t commit myself to making any major changes to the Easy File Uploader. I am already behind in a few of my project.
However, the change to check for maximum size of an image is best done with Javascript before uploading the file. As for renaming the file, I am sure what you have in mind, but that may be a little more involved that what you explain. That change may be unique to your particular setup and requirements.
@cooky61. Thanks for posting. What version of Easy Folder Listing Pro do you have installed on Joomla 4? Do you have a link to your webpage so that I can see your issue in action?
Quick follow-up… I was too quick to do a pull request on GitHub. I closed my pull request, as someone had previously encountered this problem and made a pull request 2 days ago. Here is that pull request:
in updates XML always resulted in an error #38121 In the interim, until they fix this issue in a new Joomla release, the only thing I can do to circumvent it is to remove the database requirement entirely from the update XML file.
Ok guys. Thank for coming to the support site and posting the error. Fortunately, the error is not a result of anything I have changed or my code. Actually, a change was made in the Joomla CMS code that created the error. I have researched it, and found the problem, and have requested a pull request on Joomla’s GitHub. It is now up to the moderators to review my pull request and make the change in the next Joomla 4 release. Here is a link to the pull request I made: Update ExtensionAdapter.php #38131
It seems as though the they made a change on June 11, and that is what messed it up. I am requesting they revert it back.
@serge73. Thanks for reporting. I have not changed any settings on my Update Server. The minimum MySQL Version supported by all my extensions is 5.5.3.
If your database server is version 5.7, then you should not get this error. However, where are you getting this error? Could you email me a screenshot?
