Monday, April 15, 2013

 Crystal Reports Runtime Components
In Crystal Reports Basic for Visual Studio, you can use .msi files for both ClickOnce deployment and Windows Installer deployment. The .msi file contains the components that enable clients to view applications that use Crystal Reports. If you use the .msi file on the target machine, the Windows Installer provides the Crystal Reports runtime files that are required by a deployment project. The .msi files are included with the Crystal Reports Basic for Visual Studio installation.
The following are the .msi files used in Crystal Reports Basic for Visual Studio 2008.
Runtime
Location of MSI
Crystal Reports Basic for Visual Studio 2008 (x86)
C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\CrystalReports10_5\CRRedist2008_x86.msi
Crystal Reports Basic for Visual Studio 2008 (x64)
C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\CrystalReports10_5\CRRedist2008_x64.msi
Crystal Reports Basic for Visual Studio 2008 (IA64)
C:\Program Files\Microsoft Visual Studio 9.0\Crystal Reports\CRRedist\IA64\CRRedist2008_ia64.msi
NoteNote
ClickOnce deployment is not available for the IA64 platform.
Friday, April 5, 2013
Do you want to accept inputs via voice? here is what you need to do.
working on Google Chrome browser


Put the following javascript in the head section of your html.
//adding speach recognition to an html text box 
//Start of speech
<script type="text/javascript">
function voiceInputOver(val){
     alert("Voice input is complete");
     alert("Your input is " + val);
}
</script>

and put the following line of code in the body section
<input onwebkitspeechchange="voiceInputOver(this.value)" x-webkit-speech />

//end of speech


Here is sample working code


<html>
<head>
<script type="text/javascript">
function voiceInputOver(val){
     alert("Voice input is complete");
     alert("Your input is " + val);
}
</script>

</head>

<body>
<input onwebkitspeechchange="voiceInputOver(this.value)" x-webkit-speech />
</body>
</html>
Monday, April 1, 2013
So, a couple of days ago, I got myself into this project where the previous developer have used Joomla as the platform for the whole website which had a store as well.

Everything was working just fine on the old server, however, the client wasn’t happy and wanted to move it to another hosting provider, and the trouble just began here.

Well, to make it shorter, the transfer went smoothly (or so we thought). We could login to the admin backend and everything was just fine, we could publish articles and delete old ones. All was perfect, BUT, the front end did not want to appear! That was it, just a blank Joomla home page, a blank white page, that’s it. We could login to the admin panel, but the Joomla frontend was always blank!

So, reading about this on the internet, we found many solutions, and after lots of trials and errors, we managed to solve this.

So, read on to see what was the cause of the problem.

1. (.htaccess) File

Though we have checked the file and it was completely fine, nothing could make sense of why this joomla blank white frontend was there. So, a simple solution, DELETE the .htaccess file. But, it might be wise to make a local copy of it first. Usually the file would be created by itself if it’s needed. Problem solved

2. Corrupted File(s)

Sometimes, joomla’s core files get corrupted or overwritten or deleted for whatever reason. If one of the core files is missing, chances are, you will have the blank page issue. To solve this, try to login to your joomla root folder through an FTP client. Find out what is your joomla version. (usually, this is located at /libraries/joomla/version.php). Look for the “Release” and take note of the version number. Once you have done this, head to joomla’s official website and download a fresh copy of the same version you have. All versions will be available in joomla’s archive. Now, unzip the downloaded files and transfer them through FTP to your joomla root folder and accept all replacements.

Note: it’s always a good idea to keep a backup before you do this. Note that this will not affect your existing content. However, it will affect your themes if you have modified any of the original themes that come with the fresh joomla pack.

3. Directory Structures

If you have migrated your joomla website from one server to another, chances are, there might be something extra you need to do in order to get it running aside from transferring the files and importing the database. Different servers use different files structures. While this will not be an issue for joomla’s core components, it might be an issue for third part components and plugins. So, to solve this, make sure your plugins and components point to the correct directories after a hosting transfer and that might actually solve your issue.

4. PHP Related Errors

Another error could be caused by wrong or deprecated PHP codes in joomla’s modules, plugins, or components (third party ones). To debug these errors, enable the debugging mode under the Global Configuration in joomla’s administration backend. Now, visit your website and see what errors does it display and act accordingly to fix those errors.

5. Error Logs

Try to check the Error logs under your website control panel and see if that will give you any heads up.

I guess that is it for now!

Have a great time, and if you found this useful, perhaps you could share it with your friends.

If you yourself have had any experience with a blank screen with Joomla and you managed to solve it, maybe you could just drop us a line in here and share with us how did you manage to solve it.

Archive

Recommend Us

Visitors