Spent hours on this, can someone let us know what this may be. Custom DNS works great, mobify site works but desktop site not redirecting and showing errors.
Notice: Use of undefined constant CNAME_UNSET - assumed 'CNAME_UNSET' in ourdomain/html/sites/all/modules/mobify/mobify.module on line 55

Notice: Use of undefined constant MOBIFY_REDIRECT_DEFAULT - assumed 'MOBIFY_REDIRECT_DEFAULT' in ourdomain/html/sites/all/modules/mobify/mobify.module on line 56

Notice: Use of undefined constant MOBIFY_PARAM_NAME - assumed 'MOBIFY_PARAM_NAME' in ourdomain/html/sites/all/modules/mobify/mobify.module on line 57

Notice: Use of undefined constant MOBIFY_COOKIE_NAME - assumed 'MOBIFY_COOKIE_NAME' in ourdomain/html/sites/all/modules/mobify/mobify.module on line 58

Notice: Use of undefined constant MOBIFY_COOKIE_EXPIRE - assumed 'MOBIFY_COOKIE_EXPIRE'

Comments

b1tr0t’s picture

b1tr0t commented

As noted in some other discussions, we're discontinuing support for this particular module - but NOT for Drupal!! The recommended way of deploying Mobify on all new sites (including Drupal sites) is to use the javascript redirection method. The javascript snippet for redirection is provided in the 'Deploy' panel for your site in mobify.me. The snippet is unique to each site.

Why discontinue the Drupal module?

1) It doesn't do much. It detects phones based on UA and sends a 302 redirect. The same can be accomplished in javascript making it one less "moving part" to maintain.

2) Given the limited functionality, it's not worth the effort to maintain across all versions of Drupal.

3) Phone user agents are being updated all the time. That means that someone with an older version of the Drupal module has a good chance of not redirecting newer phones. Even worse, we're finding that as the user agent space gets more and more fragmented, there are cases where devices that should get the desktop experience will be sent to the mobile site using the old rules. With the javascript we're able to use our entire device library to do detection (6000+ devices and growing constantly). We can maintain this library actively and there's no need for our users to update anything.

4) Doing server-side redirection can cause potentially serious problems for edge caching services such as Akamai and for some overzealous node caching modules.

Hope that clears things up. Please feel free to contact us directly using our community forum if you have any problems deploying the redirect javascript. You can find the forums at http://community.mobify.me/

Cheers,

Peter

venusrising’s picture

venusrising commented

We chose it implement mobile tools and browsecap. Mobify looked promising but no hearing anything for 27 days and no seeing anything related to this module not being supported on your site forced us to abandon trying to use it. The added issue of no test version that can works with javascript even as a trial prohibits one from even thinking about using a paid for service. The proof is usually in the pudding, Mollom offers a free verson and paid upgrades depending on usage and you can see right out of the gate that it is a viable solution to integrate with Drupal websites.

b1tr0t’s picture

b1tr0t commented

Sorry to hear that!

However, I have a feeling you've misunderstood some aspect of the service. Mobify offers a 100% free version of it's product in addition to paid tiers that is compatible with Drupal as well as every other CMS and custom-built site. The free version can be used with the javascript based redirect -- there are no limitations in this regard.

Apologies for slow responses on this forum -- we haven't done a good job of monitoring things here, but we generally get back to responses posted in our own support community (http://community.mobify.me) within a few hours. And of course, for paid users there's phone + direct email support with SLAs.

Best of luck!

venusrising’s picture

venusrising commented
Status: Active » Closed (won't fix)