Language switching fails for multilingual drupal site - drupal

I'm trying to build a multilingual web-site with Drupal 6 and currently I ran into a problem switching UI language. Switching language from the default one using language switcher block doesn't work and displays error message:
The selected file could not be copied, because no file by that name exists. Please check that you supplied the correct filename.
The following message gets written to a log:
An error occurred during creation of the JavaScript translation file for the language [language_name].
Drupal 6 on Windows and IIS 7.0.

Check if you have a directory called "languages" inside "sites/default/files" and make sure that this directory is writable.
If this doesn't solve the problem, check if there's a Drupal variable called "locale_js_directory" (in the "variable" table in MySQL) and check its value. If this exists, its the name of the directory in which the JS file will be created (instead of in the "languages", which is the default). Check if this directory exists and is writable as well.

It sounds like a permissions issue. Is your files directory writable? Check the status page (Admin > Reports > Status report). You might also want to check out these similar issues from other Drupal users running on IIS:
http://drupal.org/node/522066#comment-1822892
http://drupal.org/node/776392#comment-2867646

Related

silverstripe fluent locale configuration

I need help to understand the documentation for Fluent, from here Fluent config documentation
The documentation says:
"You can create locales via the /admin/locales CMS section."
When I create a locale, for example english, and then click on it I get at popup saying "Not Found".
Do I need to install the locale somewhere else before using it?
Did you run dev/build?flush=1 when you installed the module? After installation you should have everything read to go, and can start adding locales in the CMS.
Note that when you add your first locale in the CMS, the existing pages you have will not be available in that locale and you'll need to go into the Pages section and publish the pages you want to show up in your default locale.
I ran into this aswell.
The problem were missing files in the resouces folder. The 'Not found.' message in the admin panel refers to missing static assets like js and css files from the resouces folder. Open up your dev tools and inspect the 404'd requests. There you can see which files exactly are missing.

Demandware - Pipeline not found for current domain

I already made pipeline. Which is working fine. Suddenly it give error like
2015-12-18 02:39:08.091 GMT] ERROR system.core ISH-CORE-2368 Sites-SiteGenesis-Site core Storefront [uuid] [request-id]-0-00 [timestamp] "Error executing pipeline: Hello com.demandware.beehive.core.capi.pipeline.PipelineExecutionException:Pipeline not found (Hello) for current domain (Sites-SiteGenesis-Site)"
Does anybody know how to solve this?
In the event that your pipeline can not be found for the selected domain, please go trough and verify all of the following:
Double check Pipeline-Node naming
Pipeline URLs are generated by their name and your desired entry node, in this scenario, I would expect a file named Hello.xml in you cartridge's pipeline directory, and a start node named Start, would be accessed via {instanceURL}/on/demandware.store/Sites-mySite-Site/Hello-Start
Try and force upload of your cartridges
Occasionally the files on the server will not be updated correctly when a save is made; to force an update, right click your project, click Demandware > Upload Cartridges
Check your Cartridge Path
If you are using a shared instance, or your instance is re-provisioned, you may need to check your cartridge path to be sure your custom cartridge(s) are still there.
Check your Code Versions
Occasionally you may increment / change your code version - if you do, make sure that the path you select in Studio is the one that you have selected in Business Manager.
Tech Support
Should you still have issues following the four steps above, please file a support ticket and the tech-support team will be able to provide you with more assistance.

Fatal error: Call to undefined function wp_installing()

In Wordpress i can get this error message while update into wordpress4.4
how to reset my website
Fatal error: Call to undefined function wp_installing() in /home/u365143419/public_html/keerthikaprinters/wp-includes/functions.php on line 1354
Here's what helped me to fix the problem:
1) create a backup of all files and the database (highly suggest)
2) Delete all files and folders except for the folder wp-content. You will need this folder. It contains all the files for your theme and plugin.
3) Replace all the wordpress files in the install download EXCEPT for wp-content.
4) Update wp-config.php with your database credentials. They can be retrieved in your current wp-config.php.
5) Test your website. If all seems well login into your admin panel and see if the database needs updated.
Hope it helps, if you didn't already solve the problem.
The function wp_installing is a new function in /wp-includes/load.php, as of WordPress v4.4.0.
From my research/experience, there are 2 reasons for the problem (and it could be both):
1) Corrupted WordPress files, for example caused by an incomplete update installation, in which case you need to reupload (eg. via FTP) the core WordPress files (ie. /wp-admin/, /wp-includes/, and the .php files in the root of your WordPress site (although be careful with wp-config.php if you have a dev environment version too!)). At the very least check that /wp-includes/load.php includes the new function definition for function wp_installing().
2) WordPress becomes "confused" by an update installation (for example by a failed update), thinking that it is in the installation process, when it is not (or when it failed partway).
After making sure that 1) was not the problem (by doing a file comparison between the 'out of the box' WordPress files (from the WordPress zip download), doing a bit more research, and pulling my hair out), I found that there is a WordPress PHP flag WP_INSTALLING that the core uses during an update as part of handling the installation process. At my wits end I temporarily put the following in wp-config.php:
define('WP_INSTALLING', false);
and reloaded my failed/broken site, and lo and behold, my WordPress site started working! I then remove this line, and the site has been working fine since.
I can only assume that because my first attempt to update WordPress using the automatic WordPress update feature failed, and that when I then FTP'd up all the WordPress core files in attempt to do a manual update to fix it, that WordPress was somehow confused as to what state it was in (which even restarting the web server didn't fix). Forcing the WP_INSTALLING flag temporarily to false thus got WordPress sorted out internally, and allowed things to operate normally again. Interestingly after doing this, WordPress prompted me to update my database (which I did), and which seems to me to confirm that the WordPress update installation got interrupted midway and was the cause of my problems/this fatal error/WordPress thinking that the WP_INSTALLING flag was actually currently set as true.

Invalid config file in clean install - missing configuration section 'contactRepository'

I have done the following:
installed a clean Sitecore 7.5 instance
added the relevant asp.net web forms controls and pages to support the site
imported and published a content tree from an old application
Visiting the base site url yields a YSOD with the error message:
Could not find configuration node: contactRepository
Now I understand what this means - there's an expected configuration section that is missing. Adding an empty element contactRepository yields an expected message that this section is not defined.
What is contactRepository, what is its associated configuration section type, what is it for and what values should be specified in it? Alternatively, how can I turn off whatever demands this section to be present?
edit #1:
In the Sitecore.Analytics.config file in the node there are the following two lines:
<!--This configuration node is obsolete and will be removed in a future version of Sitecore. Use "contactRepository" node to get access to Contact repository-->
<contactRepository ref="contactRepository"/>
The comment is total gibberish. Which node? 'Use' how? 'get access' in what sense? How is this different to what's there?
replacing with an empty <contactRepository> without the ref attribute, commenting out this node, both nodes, and the whole tracking node makes no difference to the application's behaviour.
Looking at my local Sitecore 7.5 setup the Contact Repository settings should be in your Sitecore.Analytics.config.
The contacts repository settings relate to the new xDB stuff.
Please ensure you have the correct Sitecore.Analytics config files for 7.5.
There should be around 15 config files with new settings for xDB.
Please read this blog post for more information on the new Analytics setup.
https://www.sitecore.net/learn/blogs/technical-blogs/getting-to-know-sitecore/posts/2014/10/introducing-the-sitecore-analytics-index

Culture name is not supported

I'm receiving "culture name 'uploads' is not supported" when my ASP.NET application start. Where do I have to view/debug to toggle the error?
A full-text search for "uploads" returns 0 entries in my project.
I've deleted this folder and it solved the problem:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\8dfb04ef\44bf70fb\uploads
Do not worry, it is not a real error.
When the runtime tries to find which resource assemblies exists, it tries to enumerate folders where compiled DLL files reside. It assumes the name of the folder is the culture name, so it tries to create a culture for it. Unfortunately uploads is a folder which is created automatically by ASP.NET, and it is obviously not a culture :).
The runtime ignores some predefined folders like "hash", but not "uploads". So we have to live with it.
I am getting the exact same error. ["culture name 'uploads' is not supported"]. I do not know what is causing it but I've been able to get around it by clicking [Debug|Exceptions (Ctrl-alt-E) and un-checking "Common Language Runtime Exceptions". I do not have an 'uploads' folder or file in my project and there is nothing in my project that has anything to do with multilingual support and the error fires right off the bat when I run my project ... looking at the call stack just walks me through a whole lot of mscorlib calls. I have no clue why it's even getting called.
JumpingLethalRampage, instead of unchecking all "Commong Language Runtime Exceptions," you could uncheck just "Common Language Runtime Exceptions > System > System.ArgumentException." You don't need to uncheck all CLR items.
It sounds like maybe you have some code somewhere that is trying to set the culture based on a URL pattern (this may be tracked down if it is possible to get a stack trace). For example, sometimes I'll set up multi-lingual sites with URLs like this:
http://www.example.com/en-US/
http://www.example.com/es-MX/
I'll then have code in my base page that looks at the URL and attempts to set the culture based on the URL path. But if you tried to hit a URL like:
http://www.example.com/uploads
It would fail with an error like what you are seeing if you just blindly take the first path element and try to use it as the culture without checking it first.
If the application is it built upon DotNetNuke (and not a simple ASP.NET application), this kind of error generally occurs in DotNetNuke due to the issue described in Culture name '__page' is not supported.
If you are not using DotNetNuke, check your Application_Start code (in the Global.asax file). It might be setting the CultureInfo. Or check your web.config file for any invalid culture values.
Assuming that your search through the project wasn't restrictive (widest possible search in all files), then my guess would be that your browser has a User language set to a custom string - "uploads".
In IE, you can check via Tools -> Options -> Languages -> Add -> User defined language.

Resources