There are php errors and I'm wondering if these are causing my inability to download and upload SEBLOD apps I created using SEBLOD on my website.
These are the error messages in the php.error.log
[30-Jan-2019 17:02:26 UTC] PHP Notice: Undefined index: processings in /home/xxx/xxx.xxxx.com/administrator/components/com_cck/models/folder.php on line 220
[30-Jan-2019 17:02:26 UTC] PHP Warning: count(): Parameter must be an array or an object that implements Countable in /home/xxx/xxx.xxxx.com/administrator/components/com_cck/models/folder.php on line 220
As this are not error, but notices try disabling joomla error reporting (set it to None).
I turned error reporting on as I am trying to figure out why I can't download apps that I created in SEBLOD. These may be "warnings", but they are showing problems with SEBLOD.
The real question is are these "problems" keeping me from downloading the apps?
Hi, I suggested this as there is no general error regarding app downloads in Seblod (at least not in latest version), for others it works normally.
So your problem must be somehow related to your hosting environment or setup, there are many possible causes for that e.g. your folder permissions might be wrong or there is some protection system on the hosting (e.g. mod_security) that gets triggered and blocks access to your downloads. It is impossible to know what the problem is without either getting this info from the hoster, doing some trial an error on your side or using a dedicated supporter to connect to your system and explore this for you.
The folder permissions are not the problem. However, there might be an issue with modsecurity as I've had issues with it in the past. Thanks for the hint, that's what I was looking for - somewhere to start looking.
Mod security is not the problem - it's completely disabled for the domain and all subdomains on which Seblod is installed.
Looks like this issue isn't going to get resolved.
This issue was resolved by SEBLOD implementing an alternate download in 3.17.3. The problem was not my hosting environment after all.
What Seblod implemented is a workaround, so in the core of the problem is still your hosting. But glad it is resolved.
I'm a little confused by your reply. Two different SEBLOD people worked on this issue and neither one could tell me what was "wrong" with my hosting environment. The one that looked at it with me said everything was set up correctly and he had never seen this issue when all was set up properly. Then, they implemented the fix for everyone who has SEBLOD. So how is that a problem in my hosting environment?