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
Related
Yesterday my Web Profiler stopped working, in Symfony v.3.0.9 (on Win, with WAMP, PHP v7.0.4). Before that it worked just fine and I'm not sure exactly what happened when it stopped.
I first checked the JS errors being reported, then possible errors in dev.log, then tried clearing the cache (with cache:clear), also as an admin and also manually in file system. Nothing helped.
There are no errors returned anywhere and there are no tries from client side to even call it with AJAX. I tried restarting Apache, Wamp & Windows.
Then, I tried composer update, which naturally brought up some new, unrelated issues, and eventually I ended up installing Symfony 3.1, but still no sign of Profiler.
My HTML page does have a body, so the solution here: Web Profiler not showing up in dev doesn't help me. All other mentions of this problem usually lead to some compiling issue, which I don't have (or didn't find it yet).
I also made sure I am running in dev mode, by putting breakpoints in app_dev.php directly.
Has anyone any other/new idea what could be going on?
Addition: I also tried updating Symfony to 3.2, without Profiler appearing.
Addition #2: Just wanted to share, that the only way I can get my Web Profiler to show is, after the cache is rebuilt, go into the var/cache/dev/appDevDebugProjectContainer.php, into the getProfilerService() function and manually comment out the line with:
$instance->disable();
Ugly as hell, but I haven't find any other solution until now. At least, now I see that somehow Symfony decides, based on some internal logic, to actually not show the profiler. At least there is some logic at works.
The final answer to my "mysterious" issue was that someone in the team changed the profiler's setting in the config_dev.yml, and set the:
framework:
profiler:
collect: false
Getting that back to collect:true (which is also its default value) made it all work.
I'm working on a WordPress installation hosted by HostGator. I have added new code to a php file which is used for the home page gallery slider. The changes work on my local installation but do not appear on the live site. I have even attempted to insert gibberish code into the file to see if it would update, It did not. This leads me to believe it's being cached somewhere and not updating.
I have disabled all suspected caching plugins.
Added define('DISABLE_CACHE', true); to wp-config.php
Cleared all browser caches, and CTR + F5
Verified the code is sound
Waited overnight to see if it would update eventually
STATUS UPDATE:
I've continued to do the steps I've outlined above. I've had suggestions that it may not be the correct file that I am editing. The problem with that assumption, is that it works fine on the local host test site, just not on the live. If anyone has suggestions in that regard it would be helpful as well.
UPDATE 2:
I'm attempting to determine if my Instant Wordpress 4.3.1 runs a different php version than HostGator (php 5.2.17) but I can't find it in the documentation.
I use joomla 3.1.5, php 5.4.20
When my php was 5.3.x everything was fine but after upgrading php to 5.4.20 i cannot create new article categories!
I get Internal Server Error:
The server encountered an internal error or misconfiguration and was unable to complete your request.
This is not an issue with .htaccess (don't have any) or permissions(checked it a lot of times).
Strange thing is that when i enable debug system in global configuration the problem is solved!!! When disabling debug system problem comes back.
This only happens in joomla 3.x installations. I use the same server with joomla 2.5.x and it works fine.
Any suggestions? thanks in advance
Have you checked the Joomla forum ? PHP 5.4 is not used much and the Joomla 3.1.5 might have some modules that are not compatible with the PHP 5.4.
Just wanted to share the fix to this problem. EAccelerator was causing the issue after disabling it everything works fine
I don't think the main problem is with the PHP version.
To be able to Create New Categories do this :
In your joomla "Control Panel" page, this is usually the first page when you log in, scroll down and under CONFIGURATION click "Global."
In the new page for "Global" that open opens, look for "Default Editor", if you have not changed it before it's value should be "Editor - TinyMCE". Change that to "Editor-None." --Note that for now you will not be able to use the default WYSIWYG.
Click "Save & Close".
Now go back to the page for creating new categories, refresh it and create your categories.
To have access again to the default WYSIWYG, after you have finished creating your categories, go back to "Global " and change the editor back to TinyMCE.
Good Coding.
I have a weird case here....
I'm making a simple magento module right now. Some kind of script injection module (similar to google analytics module). I've built the admin config for that module (which is defined from system.xml)
as seen on the image. This module works very well on my localhost. But it's getting weird on the live server. The modules looks like it doesn't enabled at all although I have totally make sure it's all already enabled. Both via magento admin area and also via app/etc/modules. That admin config area never appear on live server's magento installation.
does anybody know what's the issue with this problem?
or at least tell me how and where should I debug it? I've been digging it to magento core code but getting stuck on getSingleton() function somewhere around magento core code. I don't understand that way-too-MVC stuff :p
I would be very glad if someone could explain and guide me on this
thanks :)
The most common problems are associated with case sensitivity. If you have Windows hosting, then the error in the uppercase/lowercase characters is not visible and it works. But as soon as it gets to linux hosting, the module will not work.
Check the paths in the settings and folders/files - so that they match.
Usually there are three things:
typos in xml files (validate them with validator)
cache is not cleared after installation (clear cache)
ACL rules are not reinitiated (re-save admin roles)
If you adjust the layout/add your own layout in the backoffice of magento, it's best to clear the cache (remove everything in the var/cache/ folder) and to logout and re-login.
Thumb rules while deploying magento custom module on the live server-
Deploy your custom module
Flush your all magento cache or at-least refresh them
[System->Cache Management]
If you have enabled compilation re-run the compilation or disable compilation until the testing is done.
[System-Tools->Compilation]
I was using Magento 1.4.1 and upgrade gracefully to 1.4.2. After testing if the upgrade was Ok, I made some modification in order to have a new home page layout for a store using these instruction. The modifications have been tested on a local version (Ubuntu 10.04, php 5.3.2), and worked great.
When I upload the files to the pre-prod server (Centos 5.5, php 5.2.14), and access the System->Configuration->design tab in the admin backend, my browser seems to keep loading indefinitly.
What I have done:
I copied the app/code/core/Mage/Page/* directory to the app/code/local/Mage/Page/;
I created the app/etc/modules/Mage_Page.xml, and defined the codePool to local;
What I have already checked:
I got no errors in /var/log/httpd/*.log;
I got no errors in magento's var/log/system.log;
The frontend works fine;
The backend can be accessed, except the System->Configuration->design tab;
I tried to revert my modifications to a revision before the modification were made (using svn);
I cleaned up the cache using rm -fr var/cache/mage* var/session/* directly on the server;
I restarted the server multiple time;
I even tried to get a dump of the db in production on the preprod server, with no effect. I still got the same issue.
If someone could point out anything I could have forgot.
I am ready to try anything to make it work, since it would not affect the production server for now.
After a lot of searching, we finally tried to reboot the apache server (we had to force it to reboot, I don't know why?). When we retried, everything was working as expected.
There probably was a corruption on the server that made crash only this tag.
Hope this could help someone.