I wish I knew. 

I just know that it works on 1.7 perfectly but not on 1.8. thread the upgrade was hard back when it was first release but thought it would get easier. 

The upgrade process hasn't changed, I would check you entries for path and dataroot in the datalists table

Are you trying to use the Elgg 1.7 database on an Elgg 1.8 version on the same server - with same domain name, same location of Elgg install directory and same location of data directory? If not, you would need to make some adjustments in the database as described here: http://docs.elgg.org/wiki/DuplicateInstallation.

If it's the same server you might still need to adjust at least the RewriteBase entry in the (new Elgg 1.8) .htaccess file in case you installed Elgg into a subdirectory (e.g. accessing it with http://mydomain/elgg instead of http://mydomain). The comment in the .htaccess file will tell you what to do.

And to make it clear: you are doing an "upgrade" rather than doing a fresh install as you want to continue to use an old database (and the corresponding data directory). If you don't have the old Elgg 1.7 files on the server anymore you will not need to remove them before installing the Elgg 1.8 files. But all the other steps are quite the same as described in the upgrade instructions. In any case you would need to run upgrade.php after switching to the old database. This is necessary to make the database an Elgg 1.8 database.

You also need to keep in mind that any 3rd party plugins that were present when the Elgg 1.7 database was in use on Elgg 1.7 and are now missing in your fresh Elgg 1.8 installation could result in problems, too. Best would have been to disable them all on Elgg 1.7 before trying to use the database on Elgg 1.8 now.

Check this "http://www.sitepoint.com/battle-of-cdn-comparing-cloudflare-incapsula/"

i already saw that page, yes.

from the comments:
"Even though cloudflare advertises that there are no bandwidth limits, there is a limit. I guess it’s not a fixed rate but I recently got an email about that (I double checked the sender)."

as i said, 'cloudflare' is presently faster than incapsula. however, if you watch the video in the link i posted you will see that incapsula offers/offered better security than cloudflare's apparently non-existent anti-hacking system. the load testing that was quoted in the page you gave me is from loadimpact and the test was not optimally set up to ensure the correct servers were being tested globally - as far as i know.

from my own experience, so far, i prefer incapsula. though my site is not busy presently.

Thanks for sharing!! Currently I am looking for speed.. But just in case I did not understand security for the site normally if I  need to secure my site I would prefer SSL over my site and also  I compared both solution everything seems same to me and I need to read more to understand security topic and need to get familiar with "incapsula"

There isn't in 1.7. In 1.8 you can use elgg_list_river($options) and pass types and subtypes as arrays in $options.

I wish I knew. 

I just know that it works on 1.7 perfectly but not on 1.8. thread the upgrade was hard back when it was first release but thought it would get easier. 

The upgrade process hasn't changed, I would check you entries for path and dataroot in the datalists table

Are you trying to use the Elgg 1.7 database on an Elgg 1.8 version on the same server - with same domain name, same location of Elgg install directory and same location of data directory? If not, you would need to make some adjustments in the database as described here: http://docs.elgg.org/wiki/DuplicateInstallation.

If it's the same server you might still need to adjust at least the RewriteBase entry in the (new Elgg 1.8) .htaccess file in case you installed Elgg into a subdirectory (e.g. accessing it with http://mydomain/elgg instead of http://mydomain). The comment in the .htaccess file will tell you what to do.

And to make it clear: you are doing an "upgrade" rather than doing a fresh install as you want to continue to use an old database (and the corresponding data directory). If you don't have the old Elgg 1.7 files on the server anymore you will not need to remove them before installing the Elgg 1.8 files. But all the other steps are quite the same as described in the upgrade instructions. In any case you would need to run upgrade.php after switching to the old database. This is necessary to make the database an Elgg 1.8 database.

You also need to keep in mind that any 3rd party plugins that were present when the Elgg 1.7 database was in use on Elgg 1.7 and are now missing in your fresh Elgg 1.8 installation could result in problems, too. Best would have been to disable them all on Elgg 1.7 before trying to use the database on Elgg 1.8 now.

Check this "http://www.sitepoint.com/battle-of-cdn-comparing-cloudflare-incapsula/"

i already saw that page, yes.

from the comments:
"Even though cloudflare advertises that there are no bandwidth limits, there is a limit. I guess it’s not a fixed rate but I recently got an email about that (I double checked the sender)."

as i said, 'cloudflare' is presently faster than incapsula. however, if you watch the video in the link i posted you will see that incapsula offers/offered better security than cloudflare's apparently non-existent anti-hacking system. the load testing that was quoted in the page you gave me is from loadimpact and the test was not optimally set up to ensure the correct servers were being tested globally - as far as i know.

from my own experience, so far, i prefer incapsula. though my site is not busy presently.

Thanks for sharing!! Currently I am looking for speed.. But just in case I did not understand security for the site normally if I  need to secure my site I would prefer SSL over my site and also  I compared both solution everything seems same to me and I need to read more to understand security topic and need to get familiar with "incapsula"

There isn't in 1.7. In 1.8 you can use elgg_list_river($options) and pass types and subtypes as arrays in $options.