Can't call method "ok" on an undefined value at ... lib/perl5/Test/Deep.pm line 150.
```
This means that you `use Test::Deep::NoTest` in some other loaded class, so `Test::Builder` isn't being loaded.
Posted at 10:16 PM | Permalink | Comments (0)
Dear monster.com support,
I live in Japan but want to view US Job postings (in actuality I want to view Job postings in Sweden, but can't seem to view your Swedish site in English.)
Every time I try to access www.monster.com you redirect me to http://www.monster.com/geo/siteselection.
Even if I click 'United States' (http://www.monster.com/geo/siteselection/MONS) you redirect me back to the same geolocation page.
If I click any other country I am able to access that site without issue. The only problem is that the only sites I am interested in are the Swedish site in English, or the US site (neither of which I can access.)
If you have some kind of legal/contractual obligation to prevent people outside of the US from accessing www.monster.com please state as much on your geolocation page so people don't waste your time with customer service mails and just go through a proxy.
Thanks much.
Posted at 11:17 PM | Permalink | Comments (0)
So I went with a single-user install of RVM and installed via the tutorial here.
All seemed to work well, until I tried to use some gems.
gem installs would appear to work fine, but whenever I ran my test code I would get errors like this:
/Users/naruzo/.rvm/rubies/ruby-1.9.2-head/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:37:in `require': no such file to load -- bong (LoadError)
Then I noticed that gemhome didn't seem right:
naruzo:test naruzo$ which ruby
/Users/naruzo/.rvm/rubies/ruby-1.9.2-head/bin/ruby
naruzo:test naruzo$ which gem
/Users/naruzo/.rvm/rubies/ruby-1.9.2-head/bin/gem
naruzo:test naruzo$ gem env
RubyGems Environment:
- RUBYGEMS VERSION: 1.8.10
- RUBY VERSION: 1.9.2 (2011-12-28 patchlevel 312) [x86_64-darwin11.2.0]
- INSTALLATION DIRECTORY: /usr/local/rubygems
- RUBY EXECUTABLE: /Users/naruzo/.rvm/rubies/ruby-1.9.2-head/bin/ruby
- EXECUTABLE DIRECTORY: /usr/local/rubygems/bin
- RUBYGEMS PLATFORMS:
- ruby
- x86_64-darwin-11
- GEM PATHS:
- /usr/local/rubygems
- /Users/naruzo/.rvm/gems/ruby-1.9.2-head
- /Users/naruzo/.rvm/gems/ruby-1.9.2-head@global
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :benchmark => false
- :backtrace => false
- :bulk_threshold => 1000
- "gemhome" => "/usr/local/rubygems"
- REMOTE SOURCES:
- http://rubygems.org/
Turns out I had a ~/.gemrc file that was confusing one or all of ruby, rvm, and gem.
I removed this file and all's well.
Posted at 06:07 AM | Permalink | Comments (0)
Posted at 03:37 PM | Permalink | Comments (0)
If there is a load balancer or other server handling SSL in front of your webserver, you need a way to tell Magento that it's receiving a secure connection, or else it will put you into a 302 redirect loop.
Put the following above the Mage::run...
line at the bottom of your index.php to prevent this issue without overriding any Magento code:
This example is for Amazon EC2, but if your load balancer uses a different header, just change the `HTTP_X_FORWARDED_PROTO` portion.
/**
* EC2's load balancer sets these for us so we know we're secure,
* preventing Magento from performing a redirect loop.
**/
if( isset($_SERVER['HTTP_X_FORWARDED_PROTO']) ) {
$_SERVER['HTTPS'] = 'on';
$_SERVER['SERVER_PORT'] = 443;
}
Posted at 01:04 PM | Permalink | Comments (6)
The HTTP health checker doesn't like anything except 200s.
If you have a password-protected site, allow the load balancer with something like this:
# Let the health checker check our health
SetEnvIf User-Agent ^ELB-HealthChecker IsHealthCheck=1
...
<Location />
...
AuthType Basic
AuthName Restricted
AuthUserFile /etc/apache2/htpasswd
Require valid-user
Order deny,allow
Deny from all
Allow from env=IsHealthCheck
</Location>
If you setup your LB to handle SSL, and forward 80 and 443 to your webserver on port 80, you can use these headers to determine whether the original incoming connection was over SSL:
X-Forwarded-Port: 443
X-Forwarded-Proto: https
Posted at 12:20 PM | Permalink | Comments (0)
The 語源由来辞典 can be fun to browse through.
Today I stumbled on this entry and wanted to look up one of the words in the description (ずる賢い ).
On attempting this, I discovered that they used an "oncopy" attribute of the <body>
element to display a copyright notice and prevent the copy action.
Theoretically, one could use a Greasemonkey script like the one below to disable this annoy...feature. What you do with it is up to you.
// ==UserScript==
// @name No oncopy
// @description Remove the "oncopy" attribute from the body
// @include http://gogen-allguide.com/*
// ==/UserScript==
var elements = document.getElementsByTagName('body');
elements[0].removeAttribute("oncopy");
Posted at 06:35 PM | Permalink | Comments (0)
If you're running any backend processing for Magento (unit tests, automated billing cycles, etc.) that rely on the Mage::dispatchEvent() mechanism, be careful of scope in your config.xml!
If your <events>
block is inside <frontend>
, then those events will trigger only when triggered by a frontend action (ie, someone interacts with your site using a browser.)
If you want your events to be triggered by backend processes as well, put them directly under your <global>
block in config.xml instead (note: they will trigger from the frontend as well)
You can debug missed events by peeking into Mage_Core_Model_App::dispatchEvent and adding debug, such as this (version 1.4.1.1):
public function dispatchEvent($eventName, $args)
{
foreach ($this->_events as $area=>$events) {
if (!isset($events[$eventName])) {
$eventConfig = $this->getConfig()->getEventConfig($area, $eventName);
if (!$eventConfig) {
if ( preg_match('/MY_EVENT_ONE|MY_EVENT_TWO/', $eventName) )
Mage::log("MISSED EVENT: '$area' '$eventName' ".print_r($this->_events[$area],true));
$this->_events[$area][$eventName] = false;
continue;
}
...
Posted at 01:03 PM | Permalink | Comments (0)
Posted at 12:44 PM | Permalink | Comments (0)
Thanks to the TypePad support team, I'm finally back online!
It seems like I neglected to complete a very important step after my Vox migration, but TP was very patient and understanding.
Thanks to Melanie, Jen and Kymberlie for helping me out!
Posted at 10:49 AM | Permalink | Comments (0)
Recent Comments