Title: VisualData's Replies | WordPress.org

---

# VisualData

  [  ](https://wordpress.org/support/users/visualdata/)

 *   [Profile](https://wordpress.org/support/users/visualdata/)
 *   [Topics Started](https://wordpress.org/support/users/visualdata/topics/)
 *   [Replies Created](https://wordpress.org/support/users/visualdata/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/visualdata/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/visualdata/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/visualdata/engagements/)
 *   [Favorites](https://wordpress.org/support/users/visualdata/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 82 total)

1 [2](https://wordpress.org/support/users/visualdata/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/visualdata/replies/page/3/?output_format=md)
[4](https://wordpress.org/support/users/visualdata/replies/page/4/?output_format=md)
[5](https://wordpress.org/support/users/visualdata/replies/page/5/?output_format=md)
[6](https://wordpress.org/support/users/visualdata/replies/page/6/?output_format=md)
[→](https://wordpress.org/support/users/visualdata/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[CIO Custom Field Groups for PODS] Is this supported?](https://wordpress.org/support/topic/is-this-supported-2/)
 *  Plugin Author [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [7 years ago](https://wordpress.org/support/topic/is-this-supported-2/#post-11468426)
 * Hi Jay,
 * Thanks for your interest in this plugin. Yes it is still supported. Please let
   me know if there is any issue.
    best regards.
 * Oliver
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Pods - Custom Content Types and Fields] Import relationships](https://wordpress.org/support/topic/import-relationships/)
 *  [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [7 years, 4 months ago](https://wordpress.org/support/topic/import-relationships/#post-11056186)
 * Hello, I am the developer of CIO custom fields importer plugin. I have just noted
   the email has been quoted above in this public forum, which was my opinion intended
   as a private conversation to address a particular use case. Just in case someone
   reading this thread in the future might misunderstand the quoted email out of
   context, here is the revised sentence regarding two-way relationship
 * PODS two-way relationship fields write index twice, not suitable for batch import,
   and are difficult to scale when data accumulates.
 * Scott’s comment above has provided insight on a technical level. The current 
   implementation of two-way relationship fields uses two records to represent one
   relationship, instead of looking up the same record in two different ways. This
   doubles up the work when writing to a database. If one author has 10 books, you
   will end up with 20 records for one bidirectional relationship field (instead
   of 10 records when using one way relationship). Now suppose a productive author
   has 50 books, or you have 5 similar relationship fields(each relating to 10 items),
   when a post is created/updated, the database server needs to take care of 100
   records (instead of 50 records). It will reach a point beyond what a database
   server can handle within a short period of time, especially on a shared hosting
   environment. This will cause the import to fail when writing data at high speed,
   repeatedly. The problem will get worse when your data grows.
 * In my email, I was trying to say you need a data structure to suit your current
   and future needs.
 * With that said, in my opinion, PODS is still the best plugin to handle custom
   fields with great support, and a good potential to scale up. It has provided 
   an alternative way to store custom data in a separate table (aka table storage),
   in addition to postmeta table. Some customers have imported over 20,000 records
   with the trio (WP All Import, CIO Pro, PODS) in one go.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Social Share, Social Login and Social Comments Plugin - Super Socializer] feature request: import user contacts](https://wordpress.org/support/topic/feature-request-import-user-contacts/)
 *  Thread Starter [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/feature-request-import-user-contacts/#post-7437274)
 * Thank you for the prompt feedback. I am really interested in this feature, and
   have some budget to have the code written. If you can do custom development, 
   please get in touch and have a quote.
 * best regards.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress Social Login] WordPress database error: [Column 'email' cannot be null]](https://wordpress.org/support/topic/wordpress-database-error-column-email-cannot-be-null/)
 *  [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/wordpress-database-error-column-email-cannot-be-null/#post-7110356)
 * guys, I saw external links from time to time, and wasn’t aware external links
   are not allowed here. apologies if it offended someone.
 * the pull request has been added to this plugin’s repository on github to address
   the db errors, with color highlight on code to change. it is easy to see there.
 * since external links are not allowed, you should be able to search for wordpress
   social login on github and find the pull requests.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[W3 Total Cache] Exclude Social Login from being cached](https://wordpress.org/support/topic/exclude-social-login-from-being-cached/)
 *  [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/exclude-social-login-from-being-cached/#post-6906736)
 * No worries. w3 total cache has a few caching modules (browser caching, page caching,
   db caching etc), and users can select which modules to enable. if your users 
   appeared to be logged out, but could download a fresher page showing logged in
   status after refreshing the page, it means the browser displayed the page from
   cache at the beginning, and fetched a new page from the server later. If you 
   turn on network debugging tool, for example on Firefox, you might be able to 
   see what is actually going on with the page. I noticed this issue when I was 
   debugging social login issues with browser caching turned on.
 * WooCommerce code might shed some light on how to avoid browse caching on certain
   pages, while allowing browsers to cache other pages.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress Social Login] login / registre issue](https://wordpress.org/support/topic/login-registre-issue/)
 *  [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/login-registre-issue/#post-7313550)
 * Hi Knud,
 * You can use the widget on your custom login and registration page. by default
   the authentication url contains wp-login.php. and may look like this
 * [https://example.dev/wp-login.php?action=wordpress_social_authenticate&mode=login&provider=Facebook&redirect_to=https%3A%2F%2Fexample.dev%2Fwp-login.php](https://example.dev/wp-login.php?action=wordpress_social_authenticate&mode=login&provider=Facebook&redirect_to=https%3A%2F%2Fexample.dev%2Fwp-login.php)
 * You may use a filter hook wsl_render_auth_widget_alter_authenticate_url to change
   the URL to your custom pages. see the documentation on github for details.
 * best regards.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress Social Login] Need function name for conditional loading](https://wordpress.org/support/topic/need-function-name-for-conditional-loading/)
 *  [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/need-function-name-for-conditional-loading/#post-7385816)
 * Hi,
 * If statement is not required in this case. the following statement only registers
   the action hook by the name “wordpress_social_login”. This hook may share the
   name with a function, but it is not a function.
 * do_action( ‘wordpress_social_login’ );
 * It simply does nothing before any function is added to this hook.
 * The function you add to the hook through add_action is referred to as “call back
   function”. WordPress will look for and execute your call back function at the
   above do_action statement.
 * if statement is required before adding a call back function. If the call back
   function does not exist, WordPress will throw an error.
 * I hope it helps.
 * Happy programming 🙂
 * Oliver
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[W3 Total Cache] Exclude Social Login from being cached](https://wordpress.org/support/topic/exclude-social-login-from-being-cached/)
 *  [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/exclude-social-login-from-being-cached/#post-6906734)
 * Hi Team Heateor,
 * Have you found a solution to this problem yet? I had the same issue when logged
   in using Safari, and had to refresh the page to force a fresh download. I didn’t
   have this issue on Firebox or Chrome though.
 * The PHP setting on my server encourages browser caching. The problem existed 
   before I installed w3 total cache. So the problem seems to be related to the 
   caching behavior of certain browsers, not necessarily by w3 total cache. Some
   users may start to have this problem when they activate w3 total cache and enable
   the option of encouraging browser caching. Turning off browser caching at the
   server side, and clear the browser cache solved the problem in my case.
 * I hope it helps.
 * Oliver
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress Social Login] WordPress Social Login Endpoint. 412. You cannot access this page directly. For](https://wordpress.org/support/topic/wordpress-social-login-endpoint-412-you-cannot-access-this-page-directly-for/)
 *  [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/wordpress-social-login-endpoint-412-you-cannot-access-this-page-directly-for/#post-7425848)
 * No worries. Glad to hear it works on your server too. WooCommerce team has done
   a good job here.
 * I will create a patch on Github, and hopefully it will be merged into future 
   releases when the plugin author comes back online someday.
 * Cheers.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress Social Login] WordPress Social Login Endpoint. 412. You cannot access this page directly. For](https://wordpress.org/support/topic/wordpress-social-login-endpoint-412-you-cannot-access-this-page-directly-for/)
 *  [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/wordpress-social-login-endpoint-412-you-cannot-access-this-page-directly-for/#post-7425840)
 * Hi Jeffry,
 * Does the trick work on your server? I am creating a pull request on github. If
   you find another trick that works, could you share, or create a separate pull
   request there too? This will help others experiencing similar errors.
 * thanks.
 * Oliver
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress Social Login] Major Issue](https://wordpress.org/support/topic/major-issue-7/)
 *  [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/major-issue-7/#post-7395346)
 * Hi Brad,
 * The issue is similar to [ the other problem ](https://wordpress.org/support/topic/wordpress-database-error-column-email-cannot-be-null?replies=6)
   reported in the support forum. I am using the import contact feature of this 
   plugin, and it is similar to the issues I got. I have posted a link to _[Link
   redacted – Please keep support on the WordPress.org forums]_ in that post.
 * Some Facebook contacts may not allow contacts to export their email addresses.
   When email addresses are missing from the returned data, the error will be triggered.
   You may back up your database table, and modify the data type definition to allow
   saving data with empty value when email address is missing.
 * I hope it helps.
 * Oliver
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress Social Login] WordPress database error: [Column 'email' cannot be null]](https://wordpress.org/support/topic/wordpress-database-error-column-email-cannot-be-null/)
 *  [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/wordpress-database-error-column-email-cannot-be-null/#post-7110355)
 * Hi,
 * I am using the import contacts feature of this plugin. Allowing users to import
   contacts is the main reason I chose this plugin. I have made small changes to
   the database table for the import to work. The details of changes are available
   in this post, _[Link redacted – Please keep support on the WordPress.org forums]_.
   The article is written for people who may know little about this plugin or programming,
   so a lengthy background is given too. apologies if you already know and find 
   it boring.
 * If you want to try the solution, please back up your database tables before making
   changes to the data type definition, or run the query in my post.
 * When social networks return the data, some fields may be empty. This is especially
   the case with Google+. The contacts from Google+ may be email or Android phone
   contacts who do not use Google+ at all, so email and urls may be missing.
 * It is possible to filter the returned data. The easier solution is to store all
   the returned contacts, allow the user to log in, and decide what to do with the
   missing data later. I use the second approach on my website. The full name of
   contacts can be helpful too, even if other fields are missing.
 * [@matesspace](https://wordpress.org/support/users/matesspace/), did you mean 
   your error messages appear on the web pages at the front end? It is generally
   recommended to turn off error reporting on production server. The error messages
   disclose information about your database and server, and can be abused.
 * I hope it helps.
 * Best regards.
 * Oliver
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress Social Login] Won't login user](https://wordpress.org/support/topic/wont-login-user/)
 *  [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/wont-login-user/#post-7431181)
 * Hi magicke,
 * This plugin uses a library called HybridAuth and needs exactly matching PHP sessions
   to work. The problem is most likely related to PHP sessions and cache. I am creating
   a pull request on github to address PHP session-related issues.
 * What errors did you get? what plugin or plugins are you using to create the custom
   login page? More details will help to debug and address this issue.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress Social Login] WordPress Social Login Endpoint. 412. You cannot access this page directly. For](https://wordpress.org/support/topic/wordpress-social-login-endpoint-412-you-cannot-access-this-page-directly-for/)
 *  [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/wordpress-social-login-endpoint-412-you-cannot-access-this-page-directly-for/#post-7425737)
 * Hi Jeffry,
 * Then the problem is exactly the same as the ones I had.
 * The code is shared in my blog with link provided in my previous comment. Here
   it is. This will change WordPress Social Login’s initial request URL and redirect
   URL, so WooCommerce will do the magic.
 * On my website, before using the following filter, the link looks like this:
    
   [https://tagnmap.com/wp/wp-login.php?action=wordpress_social_authenticate&mode=login&provider=Google&redirect_to=https%3A%2F%2Ftagnmap.com%2Fwp%2Fwp-login.php](https://tagnmap.com/wp/wp-login.php?action=wordpress_social_authenticate&mode=login&provider=Google&redirect_to=https%3A%2F%2Ftagnmap.com%2Fwp%2Fwp-login.php)
 * After using the filter, the link looks like this:
 * [https://tagnmap.com/wp/my-account/?action=wordpress_social_authenticate&mode=login&provider=Google&redirect_to=https%3A%2F%2Ftagnmap.com%2Fwp%2Fmy-account%2F](https://tagnmap.com/wp/my-account/?action=wordpress_social_authenticate&mode=login&provider=Google&redirect_to=https%3A%2F%2Ftagnmap.com%2Fwp%2Fmy-account%2F)
 * “my-account” is the default page slug when you installed WooCommerce and created
   pages for WooCommerce. Apparently if you have changed the page slug to something
   else, you need to edit the function below, and use your page slug.
 * You may copy the following code and paste it in your theme function. It needs
   WooCommerce installed and activated.
 *     ```
       add_filter('wsl_render_auth_widget_alter_authenticate_url', 'tag_and_map_wsl_render_auth_widget_alter_authenticate_url');
   
       function tag_and_map_wsl_render_auth_widget_alter_authenticate_url($authenticate_url) {
   
       	$authenticate_url = str_replace('wp-login.php', 'my-account/',$authenticate_url);
   
       	return $authenticate_url;
       }
       ```
   
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress Social Login] WordPress Social Login Endpoint. 412. You cannot access this page directly. For](https://wordpress.org/support/topic/wordpress-social-login-endpoint-412-you-cannot-access-this-page-directly-for/)
 *  [VisualData](https://wordpress.org/support/users/visualdata/)
 * (@visualdata)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/wordpress-social-login-endpoint-412-you-cannot-access-this-page-directly-for/#post-7425731)
 * Hi jeffryc,
 * This plugin uses a library called HybridAuth and needs PHP sessions to work. 
   According to the troubleshooting documentation of this plugin, 406, 412, or 410
   HTTP Errors are related to PHP sessions. I had similar problems with PHP sessions
   when using this plugin on WordPress 4.5.2. The login worked on Safari, IE but
   not on Firebox or Chrome. The root cause turned out to be aggressive browser 
   caching by Firebox and Chrome.
 * My problem was solved by changing the authentication URL from wp-login.php to
   WooCommerce’s login page (my-account). The filter, function and some possible
   approaches are available here [ browser cache and WordPress Social Login ](https://tagnmap.com/wp/enabling-browser-cache-wordpress-social-login-firefox-chrome/).
   If you do not use WooCommerce, its helper class on no-cache header may help you
   or your developer to implement something similar on your site.
 * If the PHP session problems were caused by the host, you will need to ask for
   help from your hosting provider.
 * I hope this helps.
 * Oliver

Viewing 15 replies - 1 through 15 (of 82 total)

1 [2](https://wordpress.org/support/users/visualdata/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/visualdata/replies/page/3/?output_format=md)
[4](https://wordpress.org/support/users/visualdata/replies/page/4/?output_format=md)
[5](https://wordpress.org/support/users/visualdata/replies/page/5/?output_format=md)
[6](https://wordpress.org/support/users/visualdata/replies/page/6/?output_format=md)
[→](https://wordpress.org/support/users/visualdata/replies/page/2/?output_format=md)