I'm trying to create a development mirror site of an ezPublish site so I can stage changes without messing up the main site. I copied the database and the filesystem and changed the ini files to point at the new database, but when I loaded the page I found that none of my objects were being loaded. So I break out the debug bar, and I find that for some reason the language_mask that is being used is incorrect...the bitfield is set to 4 while the mask being used in the query to load the page is 3.
So I poke around the ini files and I see a setting called SiteLanguageList[] which seems to set up 'backup langauges'. I found that If I set SiteLanguageList[] to:
SiteLanguageList[]=eng-US
SiteLanguageList[]=eng-GB
and my site started showing up. Yay!
However, all is not well. When I actually try to EDIT the page in the admin, every entry shows up blank. What makes things doubly weird is that it shows up in the admin as long as I'm merely looking at it. And then there's this weird discrepancy, where depending on where I'm looking in the admin, it either says that the page is eng-US or eng-GB depending on where I'm looking on the same page.
Seriously, what the heck is going on here?. If I click the edit button, nothing shows up.
Same question on ez Publish community
Are you sure that the database
was imported correctly? Please check
the database using "Setup - Upgrade
check" utilites
Clear all caches
manually (run "php
bin/php/ezcache.php --clear-all"
from ez root directory)
Check the
ez error log
(/var/log/error.log)
Check the permissions for the ez
folders (cache, settings, etc.)
Related
I'm sure this has been asked a dozen times here, but nothing I've found online or on here has helped. There's something strange about the Drupal site I'm currently working on - I've worked on 10+ other sites at this company with no problem - in that none of the code changes I make seem to have any effect. Anything I do through the admin backend appears immediately, but when I try to change the text in a custom page template and push it live, nothing happens.
What I know/did:
I know I'm pushing correctly because when I go in the file manager on the live server and look at the files I pushed, the changes are present.
I am sure that I am changing the correct file because when I try it locally and on our staging server, the corresponding pages update immediately.
I cleared out the site's cache in the admin menu, in Configuration -> Development -> Performance -> Clear all caches.
I asked the hosting company if there was a cache to clear on their end, they said no.
I deleted the uploaded theme from the server completely. The theming is still present, though the images are broken links. So the site theming is still cached somewhere. (I then replaced the theme folder)
I then contemplated quitting web development and opening an orphanage in Pakistan
What I did not do:
I did not run root/update.php. I figured this would recache the database and that wouldn't affect text in a custom page template (I also searched for that original text in the database to make sure).
Does anyone have any other ideas I could try?
It could be nginx cache on the server. Or PHP opcache could prevent you from seeing PHP code changes.
But if you still see deleted Drupal theme, it is rather some proxy or maybe something right in your browser instead of the server.
I have site build in Magento 1.7
I have installed a new shipping module Bpost through magento connect. When I installed that, it raised the error that, it is already existing plugin. After that when I accessed the site, the maintenance flag was active.
When I removed the maintenance flag and checked the site, everything seems to be working fine in the front-end. But I am not able to add or edit contents from the back-end. Click is not detecting in the existing lists of contents and when I click on add new (for cms block, page etc) the new section appears, but no action is performed while clicking save.
Why is this happening ? How can I resolve this issue ?
I recreated the site with my backup files to a new location. After that removed all the existing plugins and installed all the plugins. At that time all seems to be working fine. After that I have edited the header.phtml file and added some additional script.
The script was for getting contents and displaying it using script. After that when I run the site and went to backend everything again went to non editable mode. Now I am not able to click or edit any cms contents in the site of static blocks, products etc.
Why is this happening ? How can I resolve this issue ?
In my opinion, the problem comes from a javascript with an error that blocks the rest of the javascript. All buttons use javascript to fire events. With firebug or something similar, check which error is raised in the admin javascript and try to fix it. Using the solution that Niraj Jani gave about disabling module is a good way to check if it is really the module that blocks the javascript. If the problem is linked with prototype, it can come from the definition of blocks in php, the design template or layout...
Have you tried after claering cache?
Take Look at below link and its answer,
In Magento after installing extension Admin panel in unable to load
Delete (or move to another folder) files in /var/www/var/cache
Delete (or move to another folder) files in /tmp
From a shell, run
/var/www/shell$ php indexer.php --reindexall
You've just manually cleared your caches and re indexed your data. See if your system comes back to life.
I'm trying to activate a Wordpress theme but all I got is a blank page, also the admin page goes blank.
Version of WP is 3.9.1, Mysql 5.1 compatible and PHP 5.2.4 compatible too with WP. The theme in question is MH Magazine and I have it in another server with the same configuration and is working ok.
Even I tried to do a backup of the working site and place it in the production server and still goes blank.
I tried uploading the max_memory_limit in php and no luck. Error log and show php errors doesnt show anything, when I check only says the site name HTTP 1.1 500 - If I set wp_debug to true says HTTP 1.1 200.
File permissions are ok too.
A SIMPLE FIX FOR NON TECHIES (Like me really)
Loads of forums recommend various code changes and things to try, non of which worked, so I logically worked through the process more simply and solved it myself (in my case). White screen for everything, including front end and Admin. I tried everything going!
Essentially I'd asked Wordpress to link to a theme, which it did, but now I can't change it back. As it wouldn't automatically switch back to default themes, as suggested by others as a result of simply deleting the theme folder via ftp, I would have to force that myself. Without access to the admin panel, how would I change the link (easily)?. Well I can't, so instead I need to force the change of what it links to instead!
In the end I basically logged in via FTP, went to the wp-content folder, then to themes, located my list of theme folders and changed the theme folder name of the one recently selected and causing the issue, by just adding an x at the end (random letter). Then I changed the theme folder 'default' to the name of the theme which was causing the issue, then refreshed my site in the other window, at which point it displayed again. So the hard coded link never changed, but the basic files it links to now have.
The site was now back up, thank god! I then logged into the Wordpress admin panel and updated my version of Wordpress, as to be honest it had been a while and it was a little out of date, so a likely culprit for the cause of the error. Once updated, I then went back into the FTP window, renamed the folder back to 'default', and then removed the 'x' character from the end of the actual theme folder that I wanted to use. And ta dah, it now works beautifully with the theme I wanted! Without any fancy code changes or messing around with reinstalling or removing etc. BOSH!!
Hope this helps a few people out. (obviously it's different strokes for different folks)
To get this out of comments --- this is a community wiki answer.
Are your two servers running on the same platform (Linux? Win?) or different ones?
Do you have the same collection of plugins on both platforms?
Here are some things to try.
do View Source on your white screen of death and see if there's anything in the source view that can help you diagnose your problem.
deactivate all your plugins, then try the theme.
if it doesn't work, then this theme is broken on this server setup.
reactivate the plugins one by one. One of them will probably give you the white screen of death. Then you know that plugin is incompatible with that theme.
I followed this (first comment),
magento - category name and image in static block? to create a simple widget to display the category image and title from a static block on a CMS page. It works fine on my local MAMP version of Magento Enterprise 1.13.0.2. It's not working however on the stage / test environment Magento 1.13.1.0. (ubuntu).
It doesn't error, it's as though it's ignoring the template file (info.phtml). When I reverted to the default theme I realised I had to copy the template files to the default enterprise folder to get it to work but it did (local version). I have made sure that the template folders are in each of the themes, base, enterprise (default), MyTheme (default (which is enterprise default) & (MyTheme / MyThemeVariant)).
The only setting / configuration that appears to be different between the local and the stage is that pretty url's aren't working on the local. I have looked into the htaccess and it still isn't resolved. On both versions the native Category link Widget isn't working but i'm not sure if that is relevant.
I have disabled any extensions turned the cache off and cleared the index. Still nothing.
I have been looking for the answer, retracing my steps, altering and changing back any setting(s) I think may be relevant for 3 days now so i'm well stuck. Anything anyone can offer to try I will give it a go.
So in Magento Enterprise there is also a full page cache that you can access via the Magento Admin here : System->Configuration->System->advanced->External full page cache settings.
On the page System->Cache management, as well as disabling all the caches you should flush the Magento Cache and the Cache Storage.
You might have a 'cache' called Redis or APC, but I don't think that affects .phtml output. and if you can access the Widget in the back end I don;t think those items are the problem.
Your webserver might have a full page cache such as Varnish but I don't know how to use it or turn it on or off.
Theoretically your webserver headers might be saying 'this page doesn't update so internet providers can store local copies in their caches' - but I would be astonished if that was the case (inspect your header and inspect the Cache-control Expires and Last-modifed headers if you want to eliminate this possibility).
Your browser might have it's own little cache (which you can clear from your browser settings).
If it isn't a cache problem, in my experience .phtml files get skipped if they have PHP errors in them but you have it working on your local dev server. Could it be a file permission issue? Could it be a setting in the widget on your server that is not handled by your widgets .phtml? As alast resort, try changing your widget .phtml to a really simple file like <?php echo('test PHP output'); ?> and see if that renders - try putting the widget on different pages (ie new pages that won't be cached anywhere) and see if that get's everything through.
Could you have a namespace conflict with another module? Eg an XML file is changing your widget block XML name that sets the .phtml template? Does your widget.xml file declare <supported_blocks>...</supported_blocks> which might be excluding the block into which you are trying to render the widget?
What else? You mentioned this widget displays category information: Are you referring to a category that exists on your staging server? It will probably have a different category ID than your dev server and / or check the category is visible in the website and store.
Okay, I think I am out of ideas now.
The problem was that "Block" php file's first letter was lowercase. I changed it from info.php to Info.php and now everything works as expected.
This has been the single most frustrating investigation yet into Magento. The only thing I hope is that it saves someone a whole load of pain.
I have a Magento site in which there are about 20-25 extensions installed, among which 7 are commercial, which means that those 7 extensions are fully encrypted. Also none of these extensions use the User Roles & Permissions section, in the Admin area.
Now, a few days back, I got into a silly problem which is really taking a toll on me. I wanted to create a new User Role (from System > Permissions > Roles), where I already have 14 other Roles set. Now whenever I click the "Add New Role" button or try to edit any of the existing roles, I get the following error:-
<my-magento-site-domain>: This script is locked to another domain.
What I'm pretty sure is that this error is somewhere related to the use of extensions, but I don't know & can't understand where it is coming from. I have tried to solve this error by disabling all the extensions & clearing the full cache & deleting all the folders in the "/var/" folder, but nothing has happened.
Magento version: 1.3.2.3
I know that Magento upgradation is necessary, but can't do so due to those extensions.
Can somebody please help me in this matter? Any help is greatly appreciated.
When you say that you disabled all the extensions, how did you perform that step? I've found that the System>Config>Advanced status values are often ignored by extensions, as are various other attempts to disable. The only way that you can be certain of disabling the extension (IMHO) is to remove their .xml files from etc/modules.
It sounds like the error that you are getting is a Javascript generated error. You could grep the /js folder to find that error text to see if you can track down the source of the error. Likewise, use Firebug (or Chrome Inspector, choose your browser poison) to debug the JS error. Post what you find here...
One more option is to manually create the new role using phpmyadmin. By inspecting the admin_role table, you'll work out the syntax fairly quickly (e.g. tree_level ="1", role_type = "G". Then see if you can edit the new role through the UI.
Cheers,
JD
You can try with clean magento install without commercial extensions. Add a role and see if this happens. Then add commercial extensions one by one and test when this error occurs.
I assume that you have already searched all magento files (at least non encrypted ones) to see if there is any containing your error message...