I have downloaded the latest releases of Joomla (3.0.2) and Ajaxplorer (4.2.3).
I am trying to bridge the two for authentication purposes and have run into a snag. The current auth bridge is for Joomla 1.6... So I went ahead and figured I would give it a shot. The normal way to implement the bridge was just fine except for two things.
The "DS" in the /joomla/plugins/user/ajaxplorer/ajaxplorer.php line 14 needed ' around it...still not sure why but it got rid of the errors so I'm hoping that I'm safe in assuming that it's no longer going to cause a problem.
Originally it looked like this:
require_once ( JPATH_ROOT .DS.'libraries'.DS.'joomla'.DS.'html'.DS.'parameter.php' );
But after getting the errors I changed it to:
require_once ( JPATH_ROOT .'DS'.'libraries'.'DS'.'joomla'.'DS'.'html'.'DS'.'parameter.php' );
All I did was add ' around the DS. Got rid of the errors.
The same file from above is calling for a file called parameter.php that doesn't exist. I have manually looked for the file but didn't find it in that directory or in any other directory. Here is the actual error that I got when trying to login or do anything with authentication.
Fatal error: require_once(): Failed opening required 'C:\xampp\htdocs\joomlaDSlibrariesDSjoomlaDShtmlDSparameter.php' (include_path='.;C:\xampp\php\PEAR') in C:\xampp\htdocs\joomla\plugins\user\ajaxplorer\ajaxplorer.php on line 14
Don't worry, this is only a test server, the file path is not the same as the one that would be published.
So the question is: Does anyone know what was in parameter.php or know what joomla used instead of parameter.php that I could point ajaxplorer.php to? I'd appreciate the help!
You actually have to problems:
First, from what I can see you've used DS in Joomla! 3.0
DS has been deprecated in 2.5 and removed in 3.0. Regardless of a sever on *unix or Windows, you can just use /.
So it should look like this (which does not work anyway):
require_once JPATH_ROOT . '/libraries/joomla/html/parameter.php';
Second, JParameter (which was inside parameter.php) has been removed. Suggested replacement is JForm or JRegistry.
I can't tell you how you can fix this, because I haven't worked yet with ajaxplorer. It's just clear that you need to digg a bit inside the plugin to make it work.
Also be aware that Joomla! 3.0 is a short time support release. Soon it will be 3.1 etc.. till 3.5 which will be the LTS.
I would suggest that you have a look at Joomla! 2.5 which is already supported by ajaxplorer.
Related
Joomla q.
I tried updating my Joomla site, and that failed and I got a basic html version of my site. I tried to downgrade by extracting a former version of Joomla in the root folder. when this failed I tried to change it again the same way.
This gave me a white screen on both admin side and front end. After following the first few steps here
I'm finally getting this error:
*Parse error: syntax error, unexpected 'ini_set' (T_STRING), expecting function (T_FUNCTION) in /home/*****/public_html/configuration.php on line 98* (asterisks added)
There shouldn't be any ini_set function call in the configuration.php file. Your website is likely hacked - you should proceed accordingly. First cleanup your configuration.php file and then try this guide for quickly cleaning Joomla sites. Please note that usage of this guide is at your own risk and you must always backup your Joomla site before doing this. Also note that if your Joomla site has core modifications then they will be wiped out. Finally, keep in mind that you may still have reminiscent hacked files on your site even after implementing the above, so you clean those as well.
I'm getting an error in the admin page when I try to login, it was working fine and I would like to know if you can please help find out what may be causing the error and how to fix it. The error is:
Fatal error: Class 'Magpleasure_Filesystem_Helper_Data' not found in /home/site/public_html/app/Mage.php on line 546
The admin page is only showing the header and the error line code, the search box but the search box is not giving any results neither. However, the front of the store is working find, no issues in front. Please help, thank you
Best Regards,
Jenny
99% that you were hacked and that you didn't apply the two patches which were released by magento some weeks ago...
I have seen that issue 1 day ago at a client side of mine and they also didn't apply the patch.
check also this: https://magento.stackexchange.com/questions/64461/error-logging-in-the-admin-panel-fatal-error-class-magpleasure-filesystem-help
It also happened to me. Did not install the security patches.
Follow the steps from this post:
https://magento.stackexchange.com/questions/64461/error-logging-in-the-admin-panel-fatal-error-class-magpleasure-filesystem-help
Remove all files: app/code/community/Magpleasure/Filesystem/
Clear your cache, login should be possible now.
Check for new "Admin Users"
Patch your System with SUPEE-5344!
This happened to my site AGAIN, even after removing the magepleasure files, and then installing the 2 security patches.
I looked in the community and local folders as noted above in the way that I fixed this the first time around. This time there was one called Ma2.
I deleted the files from both places and deleted the cache folder contents on the server. I was then able to get the backend again. There was another unauthorized user, deleted it.
There is a remaining problem though. Anybody know where to look to fully delete the problem?
This is Compiler Error edit index.php, there just comment out following lines
$compilerConfig = MAGENTO_ROOT . '/includes/config.php'; if
(file_exists($compilerConfig)) {
include $compilerConfig; }
it will fix now..
This looks like an extension has been installed but not completely. The error is because Magento is trying to find the file Magpleasure_Filesystem_Helper_Data which I guess will either be under code base local or community app/code/local/Magpleasure/Filesystem/Helper/Data.php but the file is not there.
I would suggest reinstalling the extension either by magento connect or locally and deploy to your system and if you are still having issues contacting the developer directly may be your best bet.
I just upgrade my Joomla website from 3.1.1 to 3.3.6.
As found on https://github.com/joomla/joomla-cms/releases/tag/3.3.6 I downloaded Joomla_3.3.6-Stable-Update_Package.zip pack and uploaded all the files over my previous Joomla installation.
Unfortunately, I cannot login and the following error is displayed:
Fatal error: Call to a member function checkSession() on a non-object in /home/www/.../web/plugins/user/joomla/joomla.php on line 209
Line 209: $this->app->checkSession();
I did additional tests and it seems that all the "$this-app->..." command fail!
I opened the 3.1.1 joomla.php file and found another syntax:
$app = JFactory::getApplication();
$app->checkSession();
Replacing the 3.3.6 syntax with this one solved my problem, but I can see that similar "calls" are done when logout, so I would need to change them as well.
It looks like the new syntax ($this->app->) is not working in joomla.php after upgrade to 3.3.6 and now I'm afraid similar errors can occurs in other scripts.
Does someone already get similar errors, is that a known problem with Joomla upgrade, how to solve this issue correctely?
Thank you in advance for your help.
Joel
Why on earth would you do this? For a long time now Joomla has had a built-in updater that does several things beyond just copying the files to the correct location, like updating the table definitions, adding new tables, data migration and removing old files.
My guess is that your database schema is now out of sync with the PHP. You'll have to role back to your backup as there is no clear way to say if records have been damaged etc.
Once you've restored your backup, use one of the methods described in the Upgrading from an Existing Version FAQ on Joomla's Doc's site.
As this question is about Joomla management and implementation details, you may get a better answer if you, try asking on the Joomla Q&A StackExhange site in the future.
I am experimenting with Joomla 3.1.4. Whenever I add a new module the template does not show at all in the front-end. The site is blank. On disabling the new module it starts showing properly again. Even a basic hello world type of module does not seem to work and nor does a third party extension I have tried.
I can see them in the extension manager and in the module manager and they have installed successfully. Frustrated with all this I decided to install a new 3.1 template which too installed successfully. However this template does not show anything in the front-end either with my module enabled. It almost seems that there is some sort of security restriction which is disabling the template from rendering whenever any change is made to the basic installation.
Can someone please give pointers to resolving this odd behaviour?
Probably one or some of the core files required for the modules to work are missing.
Head to Global configuration and make sure your Error reporting is set to development. Reload the page and update your question with the error message.
Why not try the newer Joomla 3.1.5 (Download page)? I know that 3.1.4 had at least one problem which could possibly cause server errors in conjunction with extensions (the most likely reason for the blank page that you see).
In general, when encountering a blank page, the first thing to do should be to check the error log of your webserver!
I am working with Magento but i didn't find a very good way to debug my modules. For example, many time, i got a blank page with no php error and no apache error. For example, in backend, if one grid controller isn't well set, i don't have an error.
How to debug Magento module?
It sounds like you want to enable Developer mode. Add this to your .htaccess file:
SetEnv MAGE_IS_DEVELOPER_MODE "true"
You may also want to enable display errors in index.php:
ini_set('display_errors', 1);
The best way I have found to debug is with X-Debug in a local environment. You can also use log files to help debug in a production environment, if your unable to run X-Debug in the environment.
I've got a more detailed posting here:
https://gist.github.com/molotovbliss/2792c6c59410d75e5baf249b76413247
Consider also installing XDebug
This thread is old but useful.
Debugging tools and tricks are important as it saves lots of time of a developer.
Here is a compiled list My company Uses.
Use of Eclipse debugger: Magento is installed on a desktop using Eclipse debugger we apply breakpoints and other debugging tricks.
Use of Bug commerce as suggested in above post.
Use of Mage::log for error log and exception log.Also Magento Report files.
Use of Varien Object getData, debug.
Use of back trace: Mage::log(Varien_Debug::backtrace(true, true), null, 'backtrace.log')
Remote server level debugging.
var_dump PHP function to echo and exit.
If you are (want to be) a real Magento Developer, here is the best combination of IDE and plugin you must use to work on your Magento Projects.
First of all, phpStorm the best IDE you can find.
Exist a very helpful plugin called magicento that you can use auto-complete, find in path magento, create modules very quickly and without issue, other great stuff you can use with that plugin.
Of course need to install Xdebug (be carefully if you already run a project with ioncube, bc you need to make some trick there, Xdebug doens't work properly with ioncube loader).
This last item on the list is something I need to be reviewing but I think should be great to debugging porpoises, MagentoDebugger Chrome App.
Let me know if you need something else or any help installing some of the stuff.
Best,
Alejandro.
You can look in var/log/exception.log or system.log in the magento root. These are the directories for Magento excepetions and logs. Otherwise you might need to increase the php error log level.
Alan Storm created a Commerce Bug to help with some inline development issues.
Please try to use this magento debugger, it's chrome extension. http://w3site.org/magento_debugger it's realy speeds up a work. Just need to configure on the backend once and use Chrome extension.
Here easy to debug blocks, mails. Easy profile your extensions, etc.