Jing

hi, thank you for the reply.

This is what I found as a temporary solution following your hint.

Disable all functions except the Passwordless login and Multisite Tweak. It is very important to enable Multisite Tweak. If it is not turned on, it leads to the same error.

This suggests the issue is a bug and iThemes should look into how the multisite is handled.

Jing

And I keep getting this error:

I switched out to a different plugin. The issue went away. So it appears to be a conflict between your plugin and other plugins, in particular the Newsletter Plugin.

https://www.ads-software.com/plugins/newsletter/

I am not asking you to fix it, but trying to get some ideas on where to look for the cause.

And please advise what theme you recommend.

Cena, you are very welcome.

OceanWP saved the day as we will not write off WP Job Manager but only replace the theme.

Jobfinder theme design does not make sense in that:
1) It is confusing. If OceanWP could get the site up and running right out of the box, while JobFinder theme causes so much trouble to set up, then it is a poor product.
2) The documentation is really sparse. TinyGiantStudios claim the theme to be “incredibly well documented”.

This is their documentation page:
https://tinygiantstudios.co.uk/documentation/jobfinder-documentation/

And we read from the beginning to the end, and could not find one letter devoted to solving the widget and social button issue, as shown in this screenshot:

OceanWP does not have this issue at all. And I think it is the same like many other themes.

3) The response is really slow. We normally will wait for 2-3 days before they respond. And in the process, we likely will run into other issues which leads to more tickets, hence more backlog.

Switching to OceanWP allowed us to clear the backlogged issues in less than 5 minutes.

4) I am questioning the ability of the TinyGiantStudios to design a good user experience for its users.

For example, the appeal of Job Finder theme is tied to its display of map. This is actually a very reasonable requirement. However, the way JobFinder is designed does not make much sense. Its default is a static map image – why would anyone want that?

They can very easily utlize for example, shortcodes provided by GeoMyWP team to achieve a much more compelling design.

They did not. Instead, emphasizing their design is “incredibly well documented”.

I do not know what to say. Maybe they should include a prerequiste that to use products by TinyGiantStudios, one needs to have a Master’s degree in Computer Science, incredible patience and ability to fix design issue with their own super coding skills.

Cena, this means a lot.

We found an easy solution. So easy it took us 5 minutes to “solve” all the problems that we have been struggling for days.

We simply deactivated the JobFinder theme which is replaced by a free OceanWP Theme. As soon as we did that, the very ugly widget issue totally went away.

Now the 2 pages remain a challenge for us to totally figure out:

1) the company page. This is one thing that will make a huge difference. To convince an employer they should keep coming back to post, you gotta have a very professional company profile page.

2) of course, the single job page.

And the biggest lesson we learned is we spent too much time waiting for the TinyGiantStudios “solution” to work out.

They might have good developers with good intentions. But there is no question in my mind, their product, in particular JobFinder is a miserable failure. There is no documentation at all to guide one to make a default site like they advertised.

We had a complete clean install thinking this would be a breeze, and we were so wrong.

The fact that a free OceanWP theme would right out of box make our site look normal speaks in volume what a gap Jobfinder theme creates by itself.

We found a very simple solution: Switching to OceanWP theme. Hopefully this works with the WP Job Manager.

Stay away from TinyGiantStudios!

Update:

There is no documentation for the theme teaching the user how to set it up.

We tried and errored to find how to set the widget up.

1) Widget
So we tried both Display Everywhere and Sidebar Blog

It does not matter, both will display the widget at the bottom of the page not to the right sidebar area. It looks funny.

But if you choose Sidebar Page, then that widget which includes pages list, archive and meta, which looks so OMG ugly shows up. This one is monstrous.

2) Social media share button. The social media button looks so bad. And there does not seem a way to change the ugly look.

I am wondering who helped TinyGiantStudio design the theme? Did they specifically hire people who do not know:
– The importance of widget to a wordpress layout?
– the default look of a social media button?

And for the sake of Jesus Christ, provide some basic documentation so your users do not have to spend hours and hours experimenting with the layout.

We have to look seriously into alternatives. This experience has been horrific.

This is perfect. We look for a solution each site will have different testimonies.

We have tested your product. And got all answers. It works well with our site.

1) it does not interfere with the function to reset the password.

2) it does not break other functions.

Thanks a lot

We have an idea but will need help to complete our solution.

The solution is to build a bridge between the WooCommerce Membership and WCFM Multivendor Membership.

Here is how it looks like:

If we can import the plan list from WooCommerce Membership in WCFM Membership, and use the imported membership to link to the Groups and Capabilities, then the problem can be solved.

Is it possible? If so, how to do it?

Thanks a lot.

Jing

Yes. You are very helpful. Thanks a lot.

Sure.

Andrew, I will only contact them after confirming that Paid Membership Pro can not handle this scenario.

If Paid Membership Pro can handle this, I will go with Paid Membership Pro.

The scenario is

A user will first go through WooCommerce and choose a role between a Vendor and a customer. Then the user will be offered different levels of memberships based on these roles.

From what I read, it appears Paid Membership Pro applies when a user first registers not through WooCommerce, correct?

So it sounds like in our case, WooCommerce Membership might be easier to implement, right?

Andrew, our user will register through WooCommerce first. In the process, they will obtain a role either as a vendor or as a customer.

Then within that role, we will offer different levels of membership for them to choose from, including both free and paid.

So in this case, shall we use Paid Membership Pro or WooCommerce Membership plugin?

Jing