VisualData

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.

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.

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

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.

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

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

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, 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

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

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

“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;
}