Forum Replies Created
-
Posts
-
@jimi. Thanks for your question. Could you explain what you mean by multiple columns instead of 1 long column? What do you want in multiple columns exactly? What would that look like?
@Wilco1219. Thanks for posting your request. I just updated the module to version 3.1.2, which includes the feature to force download files when you click the link. Check it out. Hope this helps.
@serge72. In terms of the mime types. Sometimes, you have to figure out what mime type your server is detecting. I know that in some cases, the mime type detected by your browser and your server can be different from each other and also different from what they are supposed to be.
@serge73. Thanks for your question. I would have to change to code to allow the administrator to turn off this error message. Currently, as it is, it will show an error message.
Could you email me a screenshot of what exactly your users are seeing?
@Peter2. Thanks for posting your question. The script.php file is the only file not being used or installed in the zip file. It’s empty anyways, so it is not important. The icons folder is copied to the Joomla’s media folder, if I recall correctly. Language files are copied to Joomla’s language folder.
Joomla’s system does not copy all the files in the zip file to the module’s folder. This is how Joomla works. There is nothing wrong, and being free has nothing to do with where the files are located.
I think the language tag for German is “de-DE”. The language INI files related to German should be installed in
/language/de-DE. If your site’s language is set to German, it should use the German language files. @pat01. thanks for posting. Glad to know the solution was simple. Have a good one.
@jimi. Thanks for following up. Yes, it is unfortunate that I have not been able to keep to my original schedule of updating my extensions. This is due to some personal reasons, yet that is no real excuse. The only thing I can do is apologize, since I did not meet the expectations of my customers.
@shoshanaz. Thanks for following up with the link. It was very helpful.
If you Inspect the HTML DOM on on the page, you will see that you have placed the listing inside of a <pre> and <code> tag. This is what is creating the spacing and grey line. If you remove the surrounding PRE and CODE tags, you will not have those artifacts any more.
@shoshanaz. Thanks for posting. I am unable to see your pictures. Can you post or email me the link to your webpage? That way, I can look at the listing directly and see what you are referring to.
@Mark68. Thanks for posting.
OK, based on your description, I believe the issue is not with the PHP version, but rather with the setup of how the article is accessed on your site. Redirecting to the home page when you click upload usually happens when the page with the uploader is not part of the menu system.
You have to setup a menu item for the page with the uploader. This menu item could be part of the main menu, or even part of a second, hidden, menu that is unrelated to the main menu of your site. What is happening is that when Joomla calls the current Uri function, and the page is not part of the menu system, it will just return the home page Uri reference. So, when you click upload, it goes straight to the homepage instead of page the uploader is on.
If you have a public site, you can send me the link so that I can take a look, but I suspect that what I have described might fit your situation. To remedy it, all you need to do is create a menu item for the webpage (article) with the uploader.
@dabacus. This error is a false positive. It was reported by several extension developers including myself. It was fixed in the Joomla 4.2 code branch, but has not been patched in the Joomla 3.10 branch.
Unless the code maintainers apply the patch to the Joomla 3.10 branch the error will show. The only thing I could do on my end is to edit my Update Server to not include any reference to a database requirement.
@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.
