Joomla Upgradation showing error - joomla3.0

I upgraded joomla but I get this error:
Fatal error: Call to undefined method JSite::execute() in /home/digitec4/public_html/index.php on line 40
Thanks for you help.

You've got two options in order to solve this problem:
1) Upgrade Joomla (if available). You just need to go to your control panel from the administrator sub-site and upgrade.
2) Reinstall Joomla and move your directory structure to the new installation.

You need to edit only "public_html/jupgrade/libraries/cms/controller" and rename the file of the controller.

Related

Class 'SqlFormatter' is missing CAKEPHP 3 DebugKit

I've just installed the latest Debugkit from https://github.com/cakephp/debug_kit.
Everything is working. However, when I clicked on the "SQL Log", the CakePHP logo keeps spinning. I tried to debug by opening up the console.log and saw an 500 error. It shows the below.
Error: Class 'SqlFormatter' not found
File /Applications/MAMP/htdocs/App/vendor/cakephp/debug_kit/src/Template/Element/sql_log_panel.ctp
Line: 24
From my understanding, SqlFormatter class is not found in sql_log_panel.ctp. How can I add/declare the SqlFormatter class?
Just install it via composer, problem very likely solved then.
https://getcomposer.org/doc/00-intro.md
http://book.cakephp.org/3.0/en/installation.html#installing-cakephp
I highly recommend you to become familiar with composer, it is a standard tool for php developers for some time now. Composer will automatically install the dependencies for you.
Your second best option would be to download the SqlFormatter package manually from where ever it comes from and set your autoloading or include manually up.

Not able to load Drupal site

I have downloaded a new theme from Themeforest however when loading the site I m getting the below error.
Even developer is confused about the error.
I believe its more of drupal issue can anyone help?
Fatal error: require_once(): Failed opening required 'C:\wamp\www\sites\all\modules\media\file_entity/file_entity.file_api.inc' (include_path='.;c:\wamp\bin\php\php5.4.12\pear') in C:\wamp\www\sites\all\modules\media\file_entity\file_entity.module on line 13
Can you try using relative path like
require_once("./file_entity.file_api.inc");
Before that you need to find out the getcwd() for getting the current working directory.'
then give relative path according to that.
OR
use below,
require_once(DRUPAL_ROOT . '/sites/all/modules/media/file_entity/file_entity.file_api.inc');

CakePHP searching for DebugKit at wrong path

I am trying to import DebugKit and CakePHP is producing the following error: DebugKit.ToolbarComponent could not be found.
Right below it, it says:
Create the class ToolbarComponent below in file:
/Users/SomeUser/Sites/SomeProject/app/Plugin/DebugKit//Controller/Component/ToolbarComponent.php
If you notice though, there are two slashes between DebugKit and Controller for some reason, and that's obviously not a real directory. The server running PHP 5.4.17. I have followed the exact installation instructions listed here. Any suggestions?
I had the same problem and solved it by changing the permissions to 755 to folders within DebugKit.
When I encountered this problem, I realized I had a Plugin/DebugKit folder structure in my project's root, and under the app directory. The one under app was empty, save for a blank file called empty. Strange. I have no idea how this happened. (Perhaps from accidentally running composer as non-root?) I deleted app/Plugin/DebugKit, and moved the one from the project root into app. No more error.
DebugKit does not currently seem to be compatible with cakephp 3.0 even though it is the example in the documentation.
The latest version still seems to use the 2.x methods.
I will also submit a ticket regarding this to update their documentation to prevent confusion.
If there is something I missed regarding this issue and it is actually possible to install this, let me know.

How to prevent Joomla site creating unwanted folder

I have a menu link with the alias "inside" on a joomla 3.1.5 site here: http://naiwellness.com
Every morning I check the site and a folder named "inside" has been created in the root dir which prevents the site from loading as it should, instead displaying a directory contents listing at http://naiwellness.com/inside
Anyone have any ideas how to prevent this please?
Thanks
This is just a theory, but check the xml files of your installed modules and plugins (most likely a plugin) for this line...
<folder>inside</folder>
and if it exists try deleting that line of code - or better still uninstall the extension - that should fix it. It's possible that a plugin requires that folder and has php code to create the folder if it doesn't exist - and so creates the folder each time it is run - i.e. when the site is loaded. The above line of xml code I have asked you to look for will go someway to helping determine if this is the case.

DNN An Error Has Occurred

Is there a way to get details about this error? I turned off custom errors:
It looks like I am missing a skin file. How do I get it back? I used the one from the default install of DNN 6.2.4.
You could look at your DotNetNuke log4net config settings and check where you are logging errors. The default location is {DotNetNuke_Root_Folder}/Portals/_default/Logs/.
The log level by default is set on error so you can change that to "Debug" if you want by changing the element in the following config file {DotNetNuke_Root_Folder}/DotNetNuke.log4net.config
You can copy the skin's folder in your DotNetNuke installation zip file to your installed DotNetNuke website. Path to skins (DotNetNuke_Community_07.00.05_Install.zip\Portals_default\Skins)
Hope this helps.
You can get all error detail from LogViewer module of DotNetNuke
Login as administrators then go to Admin-Event Viewer , here you can find the details about error.
I had this error also; on a local instance. After installing a DNN Template via the .visx file, IIS had set up a virtual directory for the desktopmodules folder. Removing the virtual directory cleared this right up in my case. Took a long time to troubleshoot, so hopefully this helps someone avoid the wild goose chase.

Resources