I have a strange issue, I am building a custom magento theme, and all of a sudden, my custom page/catalogsearch/form.mini.phtml file isnt loading and its now loading the base/default one instead?
All my other theme files are loading correctly, and I have emptied the cache multiple times. I have tried altering my version of the file, but that doesnt make a difference either.
Can anyone think of anything to try? It's like something is telling it to override any other version and only use the original base version.
Running 1.9.2.4
Thanks.
I'm an idiot - my FTP app wasnt showing the current live verison... I logged back in and noticed my template had vanished. Re-added, altered and voila!
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'm having a serious problem. I have wordpress 3.9 installed on my server. the problem is that my website front end loads good, but my back end just loads text :
I have updated/reinstalled wordpress but nothing has happend. What should I do?
Thanks for help.
I'm 100% sure that if you simply do the following, you'll figure out what's wrong and fix it.
Deactivate all plugins without use of your WP-Admin.
Activate them, 2 or 3 at a time, and determine which plugin is the culprit
If none of these plugins are the culprit, go to the WordPress site and download WordPress. With an FTP utility such as FileZilla or another client if you already have one, then upload the entire wp-admin folder to your server, overwriting older files.
Your WordPress admin will be fine after these steps. And of course, never alter any core WordPress files -- ever. The only files you should ever tinker with are files in your child theme, which is something you should be using.
Would be great to have a bit more information about this topic. First of all: Is this a new problem respectively did the admin run without errors before? (3.9 sounds like the page is not a new clean install).
Usually I would start debugging the page via e.g. firebug => Check the Stats of the CSS-Files.
If they load correctly (200) check if they are empty or incomplete (Incompleteness can be checked via diff against the original file ... most IDEs will handle that for you)! If they aren't you have probably just diabled CSS in your browser for the URL of the admin-panel.
If they don't load, try to check why! If the files exist its most probably an error in your .htaccess (wrong rewrite, blocked directory, etc.).
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'm currently working on a wordpress website, of which I'm trying to overwrite content-extensions.php with a new version. On uploading this it appears to work, the file transfer is successful. However, there is no change in the browser even after refreshing and clearing the cache. I've also ensured that there are no plugin's caching within wordpress, and file permissions are what they should be within FileZilla.
Here's the odd bit.
If I go into theme editor, and locate content-extensions.php I can see the changes that I've made in the source code. For whatever reason they're just not appearing in the browser.
I'd be really grateful if someone could point me in the right direction for this one, as I haven't a pickle.
Many thanks.
Are you working with an extension or with a theme based function?
If it's an extension, remember to activate it, i often forget that, i upload code, see it in the extension manager but forget to activate it.
If it's in the theme, are you sure you are using the right theme and not the basic one?
I know this doesn't shed any light on why it's actually happening but I've had that before and just deleted the file and uploaded the new one rather than trying to overwrite it.