wmsedgar

Justin,

Thanks for your response; I appreciate the work the WPEC team is doing. That said, I’d recommend that the list of supported payment gateways be updated. It only hurts WPEC’s reputation when supposedly supported functionality does not work. I like the idea of WPEC, and it’s flexibility for customization. I was considering some of the additional features, but there is no way I’m going to invest money in add-ons if the core features are not rock solid.

The PayPal Express gateway appears to have similar issues in terms of handling IPN notifications. Sandbox testing results in ‘Incomplete Sale’ even though PayPal Express successfully handles the automatic charge. I can of course push the orders through the system manually, or hack the WPEC code to make it handle the notifications properly, but neither of those options are viable long-term solutions.

Based on my tests, I’m planning to go live with the PayPal Standard gateway on WPEC and see how it goes, as I’ve already invested a fair amount of time in customization of WPEC. However, based on my experience thus far I’m also going to look at alternative shopping carts.

Andy,

I’ve got PayPal Payments Standard 2.0 working (including the IPN notifications and automatic updating of the WordPress order status to Accepted Payment on WordPress 3.3.1 and WPEC 3.8.7.5 (which returns the customer to the correct Transaction Results page with an active product download link. One caveat, my configuration is set up on the PayPal Sandbox test environment, I’ve not yet gone live on the site. Your settings look fine, I’ve basically got the exact same settings with the exception that my URL setting is: https://www.sandbox.paypal.com/cgi-bin/webscr.

One question, did you also set your notification URL and IPN setting within your PayPal account profile (not your WPEC payment settings) as noted by Jason above?

I will say that this is my first foray into using WPEC, and I’ve been VERY underwhelmed by the quality of documentation and support available for the standard features. PayPal Payments Standard 2.0 seems to be the only payment gateway that works, at least on WP 3.3.1. I’ve been unable to get PayPal Express Checkout 2.0 to work OR Google Checkout. Both PayPal Express and Google Checkout do not handle the automatic order status notifications from either PayPal or Google. The test charges go through fine on both PayPal Express and Google Checkout, but are not processed correctly by WPEC. I posted on the GetShopped forums but haven’t seen any response…

Piet,

Glad we’ve pinned down the issue. At present, Googlyzer is really only meant for users with WP Admin capability, as the dashboard is only accessible via the admin console links. We have future enhancements planned to provide functionality outside of the admin context, and those could make Googlyzer more relevant in your environments. We also intend to make the browser compatibility checks and authentication token error handling more robust.

One thought is that at present, you could perform the authentication step for your customers during setup, as this only need be performed once (assuming they use the same web browser). However, as you say, they will not be able to access the Googlyzer Settings pages in order to customize the dashboard, and they would also need admin access in order to view the dashboard page, so that may not help.

Anyway, if you get a chance, please update your works/broken vote in the WP Plugin Repository, as I think we’ve identified the plugin is not broken, it’s just that it doesn’t provide the functionality you need at present. Thanks again for your feedback. It’s always helpful to hear different usage perspectives to help drive future updates.

Piet,

We appreciate your situation. Unfortunately, the information you provided doesn’t give us a lot of data with which to diagnose your problem. Generally, it sounds like you may have tried to access the Googlyzer dashboard before authenticating with Google and saving your settings. Some notes:

1. BEFORE accessing the dashboard, you must ALWAYS go to the General Settings tab and follow the instructions to authenticate with Google, grant access to Googlyzer for your analytics data, and then SAVE your settings. Otherwise Googlyzer has no means to retrieve your analytics data feed and build the dashboard. We have only seen 400 errors in test when the authentication step had not been done prior to accessing the dashboard.
2. Another potential scenario: when switching between browsers, did you go back to the General Settings page and repeat the authentication and granting access process with Google Analytics? If not, this could explain your issues. Each browser stores it’s own authentication token (cookie), and these are not shared between browsers.
3. Another possible (less likely) scenario: did you have multiple browsers open with active sessions connected to Googlyzer when you received the errors? We have seen issues with the Google authentication mechanism when another browser is open with an active session that is also authenticated with Google.
4. Another possible (less likely) scenario: were you signed into another Google account via another browser tab or browser window while performing the authentication process for Googlyzer? If so, this can cause Google authentication and grant access process to fail.

We are also curious what browser version(s) you tried, as older browser versions do have issues with javascript function support.

We’re currently working on Googlyzer v1.3, and hoping to incorporate some more graceful error handling, as well as additional browser compatibility checks. We hope you’ll give Googlyzer another shot down the road.

In the meantime, we’re going to mark this issue resolved. Let us know if you’re interested in working with us to diagnose further.

Piet,

Thanks for your post. We’re happy to assist with issue resolution. Can you provide more information and the specific error message? Errors encountered have been easily resolved thus far. There are FAQs, and common basic errors/resolutions listed in the Googlyzer Web Forums, did you try any of those?

We’ve tested Googlyzer successfully on various OS/Browser configurations, and also noted some platforms with issues, due to JavaScript function support within the browser. The list is available under the Other Notes link on the Googlyzer plugin page in the Repository.

Regarding your specific error:

• When did you receive the error? (what were you doing)
• What was the specific error message?
• What OS and browser version(s) were in use when you received the error?

3Plumes, great! Glad to hear that worked for you, and that you like the plugin. Let us know if you have an idea for a feature to add. If you get the chance, please submit a rating and works/broken vote!

3Plumes,

Ok, that error is easily resolved. It’s due to a domain registration issue with Google that prevents the authentication token (cookie) from happening correctly (which is why the Website Profile dropdown is not populating for you. What is tricky is that if you registered the full domain address – e.g. https://www.themomspa.com – and then are accessing it via the shortened URL – e.g. https://themomspa.com – you’ll receive that error.

See this topic on the Googlyzer Support Forum and follow the steps outlined there to resolve. It’s quick and easy, shouldn’t take you more than 5 min. If after following those steps your issue is not resolved, let us know and we’ll work with you to get it fixed.

BTW – we took a look at your domain, https://themomspa.com, very nicely done! It looks great. Are you using a custom WP theme you developed?

Marc, the above changes were included in the Googlyzer v1.1 release. We’re going to mark this as resolved. Let us know if that is not the case.

3Plumes, thanks for your post.

Did you receive an error message? Googlyzer v1.0 and v1.1 have both been tested with Google accounts that have multiple Google Analytics website profiles associated. Googlyzer is designed to populate the Website Profile dropdown on the General Settings tab of the Googlyzer Options page with available websites once the user has authenticated with Google and granted Googlyzer access to Google Analytics data. Did the Website Profile dropdown fail to populate?

In the current version of Googlyzer, in order to view data for a different website/domain, the user needs to return to the General Settings tab of the Googlyzer Options page, choose a different Website Profile selection, and hit Save. Then the new data should appear once the user returns to the Googlyzer Dashboard.

In order to view analytics data for a website/domain that is associated with a different Google account, the user would need to return to the General Settings tab and click Logout. Then the user would click on Access Google Analytics and proceed back through the authentication and grant access steps for the new account. Once this is done the user would select a new Website Profile, Save, and off you go…

Does that make sense?

Thanks for your post. Googlyzer has not been tested on WP MS, but it has been tested and runs fine on a standard WP install.

The error you noted is a path error. Googlyzer looks for the settings html file in the base plugin path, it’s standard path is:

BASE_URL../wordpress/wp-content/plugins/googlyzer/html/settings.htm

Googlyzer gets BASE_URL from running the get_bloginfo(‘url’) function. However, I believe get_bloginfo may return a sub-blog address on WP MS, and not the root URL.

Try editing the googlyzer.php file as follows:

Add this line at the top, just after the // define constants comment on line 51:

define( 'BASE_URL', network_site_url() );

Then modify the line that defines GOOGLYZER_PLUGIN_DIR (was line 54) as follows:

define( 'GOOGLYZER_PLUGIN_DIR', BASE_URL .
	'/' . PLUGINDIR . '/' . dirname( plugin_basename( __FILE__ ) ) . '/' );

Let me know if that resolves your error. If so, I’ll incorporate the change into the next version.

Ok, thanks for the additional info. As you may have already found, there is a post on the Googlyzer support forum related to the initial error you listed ‘…malformed request… domain not registered…’ here.

If you are absolutely certain that your site is already registered with Google correctly, then look at 1 of the following to resolve:

1. What URL is registered with Google Analytics? If it is https://www.modelcrowd.com, then you need to do 1 of 2 things. 1 – try using the full URL (including ‘www’) when accessing the site (including your WP admin console), or 2 – also register https://modelcrowd.com (without ‘www’) with Google. Google doesn’t seem to recognize that both URLs are the same domain (though it certainly seems like they should).
2. Check to make sure you’re signed into Google with the account that is associated with Google Analytics (if you have multiple Google accounts and you’re signed in (via any other browser sessions with a Google account that does not have a Google Analytics profile, then authentication will fail).

With regards to the last error you listed, this does not appear to have anything to do with Googlyzer. Googlyzer does not have any means to alter or remove pre-existing cookies or authentication tokens. Are you perhaps using the Google Site Verification plugin? If so, I found this thread of support posts related to this error.

Let us know how these suggestions pan out, we’d definitely like to hear whether your issues are resolved.

Can you elaborate? We’ve tested running Googlyzer while having a simultaneous direct connection to Google Analytics in another browser window in Firefox, Chrome, and Safari with no issues discovered. Not sure what issue you encountered.

Right on. Thanks!!! Had another user report it as well. We’re working on Googlyzer v1.1 now, and will incorporate the fix to the CSS.

Thanks for the post, worked for me too. I just wasn’t sure where to put the .htaccess file. I’m using Ubuntu 10.04 and WordPress 3.1.1.