I'm getting this error when trying to add posts as admin in Kunena forum. The post is not a duplicate so I don't understand why it is giving me this error. Is there something I can change to fix this problem?
Firstly, ensure you are running the latest version of Kunena (3.0.2) and Kunena plugins, along with the latest version of your Joomla series (2.5.14 or 3.1.5)
If you're running Kunena 1.6.5 and Joomla 1.7, then there are known issues with what you have reported, and thus my first point most definitely applies.
If you're using JomSocial and the JomSocial Activity Stream, again, ensure you running the latest version else try disabling the Activity stream extension to see if this solves the problem.
If you're using the Kunena/JomSocial plugin, then in its configuration set "Core Application" to "Yes" (default is "No")
If none of these fix your problem, then I would suggest reporting the error to the Kunena dev team.
Hope this helps
Related
I am working on a Drupal 8 site.
Node Add/Edit page is showing blank.
Following are steps taken to find out error:
Recent Log Messages (No Error logged)
PHP Error Log file (No Error logged)
Set memory_limit to -1 and other PHP settings related to
memory in case memory is exhausted.
Uninstalled Custom modules.
Changed site theme from custom theme to core theme.
NOTE: All other forms are working(block add/edit, etc..)
Please let me know if any of SO people faced this issue before.
We fixed my problem ourselves.
We found no error in modules and themes.
So, we decided to restore and old backup.
After the back up was restored, the functionality: Node Add/Edit started working.
I update Joomla to the most recent version (3.7.1).
Also update the Joomla component SobriPro to the most recent version (1.3.7).
Before the updates all works fine, after the updates the SobriPro component always responds with an empty page. Accessing SobiPro client or administration pages always retune a blank html page.
I already consult the administration and client Joomla error logs but nothing is register. I also try to run Joomla in debug mode but not getting any message.
Sure I run the updates first in a local dev environment.
In the local server all runs OK, I only have problems in the production environment.
Finally I found the problem. In my production environment dosen’t have the Phar extension available.
The difficult to detect this limitation was because the sobi component return black pages without reporting any error.
To correct the problem I just uncompressed the sobi framework file and make a change in the sobi component loader code. This change is documented here: https://github.com/Sigsiu-NET/SobiPro/pull/8
I've made an extension update at my TYPO3 6.2.19-Website, but the update failed, so I step back to the previous version of the extension fluidcontent.
Now my Homepage is a blank, white Page, but all other subpages are still there. At the backend, I've get this error after login:
$hookObject must implement interface TYPO3\CMS\Backend\View\PageLayoutViewDrawItemHookInterface
TYPO3 6.2.19, PHP 5.6.20, Configuration presets Development, ...
How can I recover my Website? What 'tells me' the error message at backend?
the problem has sth. to do with fluidcontent, because every page (uid) with fluid content elements was false. So I've got the latest fluidcontent who supported TYPO3 6.2- it's 4.3.3. Nothing happend at all ... I've got still the error message (s. initial post)
After a long time .. I also change the flux to 7.3.2and that was it. I've made a mistake to update the ext. fluidcontentan flux, but the latest versions do not support TYPO3 6.2.
In my case downgrade flux - solved this problem. Look flux compatible with TYPO3 6.x or 7.x and use just 6.x compatible
I tried installing an extension, and it said some core files where it wanted to install along where upgraded. I'm thinking it downgraded them so I upgraded again. I cleared the magento cache and now I'm getting a 500 error on every other page except the homepage.
Need help here. Any help is appreciated.
Using magento 1.9.
This is more a comment, but for readability I post it as answer:
Release Date is 2013-08-09, so it is max. compatible with 1.7, but a comment on
http://www.magentocommerce.com/magento-connect/e-reactor-slider.html
says that it also broke 1.7.0.2.
See installed files:
http://connect20.magentocommerce.com/community/Ereactor_Slider/1.0.0/package.xml
Download-Link:
http://connect20.magentocommerce.com/community/Ereactor_Slider/1.0.0/Ereactor_Slider-1.0.0.tgz
Releases (first and only release):
http://connect20.magentocommerce.com/community/Ereactor_Slider/releases.xml
So you could try to deactivate it in app/etc/modules/Ereactor_Slider.xml:
<active>false</active>
If that brings no success try to uninstall it and clear all caches again.
The developer is a company and has a shop for the extension with a contact form:
http://shop.e-reactor.dk/contacts/
Maybe they can help?
Good luck
I have the following error periodically show up in Joomla 3.0/3.1/3.2 articles (front-end):
warning
JLIB_FILESYSTEM_ERROR_PATH_IS_NOT_A_FOLDER_FOLDER
JLIB_FILESYSTEM_ERROR_PATH_IS_NOT_A_FOLDER_FILES
It first shows up right after install, and then disappears upon refreshing, but reappears at random times later. Does anyone know about this?
BTW, I know very little about MySQL and PHP other than setting up a database and coding a template, so if you could be descriptive, that would be awesome :)
EDIT: Maybe it's because I am installing a pre-configured package with Akeeba? But I'm pretty sure I have got this message even when I installed the actual Joomla package.