If you have upgraded to WP-Recaptcha 4.0 or 4.1 and are now receiving this error message
ERROR: Global site keys are not supported
There are issues with the 4.0 and 4.1 WP-Recaptcha plugins.
Solutions:
1) roll back to 3.2. Download it from me, here
2) change plugin to something else
** DO NOT UPDATE To 4.0 or 4.1 if you are using WP-RECAPTCHA
By default, ASPMAKER 11 (and higher) come with the basic CKEDITOR toolbar.
If you wish the full capabilities of CKEDITOR:
1) deploy out your normal ASPMAKER project folder to the web server
2) go to http://ckeditor.com/addons/plugins/all and use the “CKBUILDER” on the right side to build out your custom build of CKEDITOR (I just took “everything”).
3) save the file
4) extract, and overwrite your existing CKEDITOR file inside the ASPMAKER folder on your server.
5) edit the CONFIG.JS file and add this line config.allowedContent = true;
that will make sure you can save HTML without certain tags getting stripped out.
very easy… first import your MP3’s into your local song library within iTunes.
Select all the MP3’s you want to reclassify as Podcasts (and use the Podcast app).
Right click and “Get Info”
Go to the OPTIONS tab
select the “Media Kind” drop down and choose “Podcast”
all the selected MP3’s will now be moved over to Podcasts in your library.
You can now choose to sync them to your Apple device and use the Podcast app to listen.
Very easy fix.
Edit the config.js file (inside the CKEDITOR directory)
add
config.allowedContent = true;
before the close bracket tag.
save the change.
Edit the ewcfg11.asp (or slightly different filename depending on your version of ASPMAKER)
set this line to FALSE:
Const EW_REMOVE_XSS = False ‘ True to Remove XSS / False to skip
quit the open web browser (all open instances of that browser).
launch the browser.
retry pasting IFRAME code into SOURCE on CKEDITOR. Should work now.
Are you having an issue with the FIND MY FRIENDS app not showing your photo?
I am on IOS 7.x and have this problem on two phones. This is how I solved this issue.
Here are several steps to remedy this:
The above solution fixed two of my iPhones which are on IOS 7.X
We recently added a second xbox 360 into our house and came across the dreaded NAT TYPE “moderate”. I needed both xbox’s to get to “OPEN” NAT type so that online multiplayer games will function perfectly, but had to invest multiple hours of time into the process to work it all out.
The main factor for me is that I need a firewall that supports both multiple game consoles, as well as the ability to do site-to-site VPN via the firewall.
I tried the following firewall setups:
If you are able to get a Playstation Vita working with NAT TYPE 2 using PFSENSE I would appreciate knowing your exact setup.
Upgraded to PFSense 2.0.3.
My current configuration (Which is working perfectly) is as follows:
1) DHCP server ON inside PFSENSE. Both XBOX’s assigned a static IP (VIA DHCP MAC ADDRESS RESERVATION) so that their internal IP’s stay fixed. (Note: One of my XBOX’s is a newer black wireless model, the other is an older White model with the USB Microsoft Wireless adapter). I use a high end MERAKI wireless access point to get them into my LAN.
2) These are my UPNP Mappings (note my two XBOX’s are 192.168.6.234 and .234).
These settings work perfectly – OPEN NAT and my kids have played HOURS on this configuration.
The fix for this is very simple and will work under all the common browsers. This has been tested on IE9, Firefox 13, Safari and Chrome.
locate this line on your HTML page (or template):
<link href='http://fonts.googleapis.com/css?family=Dosis:400,700' rel='stylesheet' type='text/css'>
and change it to this:
<link href='//fonts.googleapis.com/css?family=Dosis:400,700' rel='stylesheet' type='text/css'>
This simple change will make your browser call the Google Font page in the applicable mode (HTTP vs HTTPS).
Enjoy!
I recently came across this issue and it was relatively simple to fix (for me)…
We participate in the BOINC CUDA project to use idle CPU and GPU time for scientific research purposes.
We recently updated to the newest NVIDIA drivers for Windows 7 x64 which are version 270.61.
After doing this we noticed the core clock on our NVIDIA Geforce 480 would drop from a standard or overclocked speed, down to 405mhz. The core clock would stick there and the only way we can get it back is to reboot that machine. Then after a few minutes again running the BOINC app, the core clock would drop to 405mhz again. (We can see this because we use the MSI Afterburner 2.1 app, which has a nice real-time graph that shows current clock, memory and GPU utilizations among other things and also allows you to overclock the card.)
It turns out that there is some new “feature” (or bug) in the NVIDIA v. 207.61 drivers that is causing this issue.
Our solution was to uninstall the 270.61 drivers, restart and then install v266.58 drivers (which are the ones that preceeded 270.61).
After a reboot and more testing the core clock speed stay at the factory default speed (700mhz) or at our designated overclocked speed, without ever dropping down to 405mhz.
Apparently this is a widespread issue and users playing 3D based games also experience this issue as dropped frame or sluggish framerates while gaming… those users should also think about reverting to 266.58 until NVIDIA gets this sorted out.
We’ll have more information after we test the next version of NVIDIA’s drivers.
UPDATE 06/22/2011: The same “clock drop” is also experienced on the most current NVIDIA 275.33 drivers. Don’t use those if you plan on using CUDA.
One of the computers in our office is an ASUS G73jh which is a powerful laptop we use for testing sites and on-location visits to clients. We usually keep the very latest Windows 7 updates and ATI video card drivers (11.4) on the machine. Recently we noticed the machine locking up after a few minutes running 3D graphics. The only recovery is to hold down the power button and power cycle the computer. The issue was easily replicated using FURMARK or BURN IN TEST. After much research we determined this is the infamous GSOD or “Grey Screen of Death”.
This is what it looks like:
ATI 5870 GSOD Grey Screen of Death
We tried everything to eliminate this issue that we could think of, even uninstalling the current video card drivers and going back to the ones on the ASUS site which are from 2009. Nothing would cure this issue, so we RMA’d the laptop back to ASUS. A week later we get the laptop back with “all tests passed, no problems” and the machine had been wiped back to the factory OS defaults for Windows 7 Home Premium.
At that point I reloaded the FURMARK and BURN IN TEST applications on the laptop, and guess what – it did not go into GSOD when running 3D. Now I immediately thought this is a driver issue with the video card, because I was trying to use the latest ATI Cataylist drivers, and this wiped laptop had a clean set of factory drivers. Not wanting to keep 2+ year old drivers on my laptop (which was purchased mid 2010), I set out to try and get to the bottom of the issue.
I found two forum sites with hundreds of pages of user posts on this exact issue. First one Here Second one here
The issue is that the video BIOS on the onboard 5870 video card is old and is not compatible with the latest ATI drivers, so what needs to happen is you have to do is flash update your video card and then install the latest video drivers from ATI (in my case they were version 11.4) from the ATI SITE here.
Here is the path I would recommend:
Note: if you still experience some other form of glitching with your video card drivers on the G73, use this procedure to completely wipe the ATI drivers, then re-install the latest ones. Try using this procedure below to get a completely fresh install of the ATI drivers.
ATI DRIVER CLEAN START GUIDE
(Modified by The Amixa Web Guru. Original one by steviejones133)