I broke my WAMP installation testing Facebook App locally. I could no longer get into PHP myAdmin.
I found the following link. The first advise is the one that worked for me.
C:\wamp\alias. Open the file
phpmyadmin.conf and change
<Directory "c:/wamp/apps/phpmyadmin3.5.1/"> Options Indexes FollowSymLinks MultiViews AllowOverride all Order Deny,Allow Deny from all Allow from 127.0.0.1 </Directory>
<Directory "c:/wamp/apps/phpmyadmin3.5.1/"> Options Indexes FollowSymLinks MultiViews AllowOverride all Order Allow,Deny Allow from all </Directory>
I recently had component that pulls facebook photos into a Joomla 1.5 site break. It didn’t pull the photos in. The component’s developers blog didn’t have my fix.
I got lost in setting up Facebook App account connected to Heroku, when all I needed was an AppID and a App Secret. I was confused by canvas page and other parts. It turned out all I needed to provide was a name and the actual URL of the site that had the component installed. I was trying to run it localhost. It looks like that toolkit can be used for building apps locally.
You also need to give your app some time to propagate to their servers.
I installed the Heroku toolbox on my win 7 machine. The next step to setting it up was to use the command line to login.
Start at the command line and type in “heroku login”. I entered my email address and password associated with the account. Came back with, “Could not find an existing public key. Would you like to generate one? [Yn]”. I typed y and hit enter, and I got the following:
“Could not generate key: ‘ssh-keygin’ is not recognized as an internal or external command, operable program or batch file.”
Searched the web and found that installing Git from this site http://git-scm.com/download/win made it possible.
After downloading and installing Git, I went to C:\program files(x86)\git\ and clicked on the “Get Bash” short cut. A command line prompt opened. I typed in the same thing as before, “heroku login”. It asked for email and password. Asked me to generate a key[Yn], I typed y, hit enter and everything worked this time.
Setting up a GoDaddy hosted MySQL database that needs to read by another website hosted on another hosting account. In setting up the database you will need to specify to Allow Direct Database Access
Here is what I did. Create a new database and click on Additional tab to expand your options. Click the radio button on the bottom.
I exported the old data from a database I wanted to keep and imported into the new one so it can be read from another site on another host.
Running WAMP version 2.2 I was testing a joomla site that was going to need to connect to an external mysql database. I used a file that was on the local host calling to the external database resource, but it didn’t work. I learned that Fopen Wrappers was set to “0”. This is the error.
Specifically “allow_url_include=0” was the issue.
I opened php.ini and searched for “allow_url_include=0”, but nothing returned. Turns out “allow_url_include=0ff” is what it was set to. I changed the value from “off” to “on”, restared WAMP. No more error.
No data was received to import. Either no file name was submitted, or the file size exceeded the maximum size permitted by your PHP configuration. See FAQ 1.16.
Turned out i just need to increase the upload size. Here is how you do it.
The first things to check (or ask your host provider to check) are the values of upload_max_filesize, memory_limit and post_max_size in the php.ini configuration file. All of these three settings limit the maximum size of data that can be submitted and handled by PHP. One user also said that post_max_size and memory_limit need to be larger than upload_max_filesize.
I have an Joomla 1.5.15 site that I should have been upgrading, but was afraid to ask the client for money. The data center and website got attacked. Site is back up but we want new hosting. There is a VirtueMart component installed, JCE, other extensions and some custom PHP modules. Not just a basic install.
Joomla.org has a good write up about it. Here is a link to it.
Here is what I am doing.
- Install Akeeba backup.
- Download backup
- Using WAMP I put the backup in a directory.
- Create a database in PHPmyAdmin
- Download Akeeba Kickstart and extract my current site to a local.
If all goes well locally I will either repeat the process on the live site. If the migration goes bad on the live site, I will use my local version. I will delete the live site. Package up my new local site with Akeeba and use Kickstart on the live site to get the site backup.
Here is complete documentation from Joomla.
First thing when upgrading from 1.5 to 2.5, the 1.5 must be the Joomla 1.5.26 version. Download the upgrade package you need to get your site to 1.5.26. You simply copy all the file over and overwrite them. The administrative area will now say “version 1.5.26”.
Second thing is Joomla 1.5 to 2.5 is a big deal. Requires jUpdate component to get it done. It took me a couple of times to get this to run. Even after enable system Mootools upgrade plug-in. Curl settings on my localhost needed to be changed.
Just below there was tiny text that read “406: cURL not loaded”. I didn’t get this every time I tried the updating.
I got this error when I started WAMP:
Google lead me to this link: http://stackoverflow.com/questions/10939248/php-curl-not-working-wamp-on-windows-7-64-bit
I used this link to get the cURL dll: http://www.anindya.com/php-5-4-3-and-php-5-3-13-x64-64-bit-for-windows/
Scroll down to “Fixed curl extensions and select your version of PHP.
Exit WAMP and unzip the one file in the zip into the c:\wamp\bin\php
php5.3.13\ext folder. Restart WAMP and install finished.
Doing an upgrade with WAMP & PHP 5 required me to do some more work with CURL. I found this article that got me started on getting past the “Checking and cleaning” dialog box.
I finished an upgrade to a Joomla 1.5.25 website with Lyftenbloggie running to a Joomla 2.5.x running EasyBlog.
First there was upgrading Joomla 1.5.25 to 1.5.26. I used Akeeba and backed up the site. Downloaded that package and used Kickstart to get the site installed locally. The upgrade went fine and I applied that to the live site. The commenting issue with the site didn’t get fixed.
Next i needed to install EasyBlog. I purchased the 79.00 pro version, downloaded the 1.5 and 2.5 versions, and installed the 1.5 first. Then I could migrate from Lyften to Easy. Easy didn’t install from the zip, so I unzipped the files into the tmp folder of the website and used the “install from directory” option and that worked.
From there I did a jUpgrade on my local site. Deleted all the 2.5 database entries for EasyBlog. I needed to export all the 1.5 EasyBlog database tables and import them into the 2.5 database.
I then deleted all the files in the 1.5 tmp directory and unzipped the EasyBlog 2.5 install files and used the same path to install EasyBlog into the Joomla 2.5 site.
The template needed to be rewritten to comply with 2.5 standards and reinstalled.
Finally I installed Akeeba and backed up the 2.5 local site. Used FTP to get the files on the new server. Uploaded and ran Kickstart and in minutes the site was up and running.
I Here is a thread that got me started.
In case the page gets lost here is the steps.
1. Open up PHPMyAdmin tool that is provided by your hosting provider and open up your current site’s database.
2. Make a sql dump for all the tables that has the prefix of jos_easyblog_*
3. Download the .sql file and save it on your desktop.
4. If your new site’s database prefix also uses jos_ , then you can skip this part. However, if you are using a different database prefix, you’ll need to edit the .sql file that you’ve just downloaded, and do a search and replace of jos_ with your new database prefix.
5. Open your PHPMyAdmin and this time, open up your new site’s database.
6. You should see an import link at the top. Click on that, and click on browse. Select the .sql file and click the run import button.
7. Install the latest EasyBlog on your new site
8. Enjoy blogging! If you have any problems at this point, drop us an email and we’ll take a look at this.