Chris Burbridge

I am having the same issue. As far as I can tell it affects all sites.

It happened after I updated a few plugins (nothing major or obviously dramatic.)

In my case the only role that exists is Customer (I think what WooCommerce puts out). And yet, I am still able to edit most of things, and even create other super-admins!

But things that require a reference to roles, the site doesn’t know what roles are supposed to be in there.

It’s a problem.

The Paypal documentation is somewhat enraging, as they have recently “updated” their interface so that My Selling Tools no longer exists; however, even their documentation still references it! I do not like to think about working for a company that must be that dysfunctional. But anyway, you all need to change your documentation.

It’s possible to access the credentials you’re talking about via the top menu:
Tools > API Credentials > NVP/SOAP API integration (Classic). A great deal of confusion was caused by not naming which type of API setup was needed, because there are 4 or 5, and the documented route to get there was changed.

Nevertheless, as I suspected the credentials were set up perfectly by the WooCommerce gateway already–entering them manually did not change the settings or the outcomes. (And I did try turning all possible plugins off and changing the theme.)

Something else is going on.

Thanks.

PS, I am happy to try to check the API credentials manually, if you give some hints about where to find them on PayPal website, because they are very hard to find ??

Hi, thank you for the fast response!

I did try turning on the log, and the output did not look like an error report. I am assuming of course that the log is for wc_gateway_ppec_xxxxxxxxxxxxx.

I also did try going to Twenty Seventeen and turning off all plugins except WooCommerce and the WC PayPal Gateway. The report looks like:

09-13-2018 @ 13:48:08 – WC_Gateway_PPEC_Client::_request: remote request to https://api-3t.paypal.com/nvp with params: Array
(
[METHOD] => GetPalDetails
[VERSION] => 120.0
[USER] => xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[PWD] => xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[SIGNATURE] => xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
)

09-13-2018 @ 13:48:09 – WC_Gateway_PPEC_Client::_process_response: acknowleged response body: Array
(
[PAL] => xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[LOCALE] => en_US
[TIMESTAMP] => 2018-09-13T20:48:08Z
[CORRELATIONID] => xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[ACK] => Success
[VERSION] => 120.0
[BUILD] => 46457558
)

Of course I have obscured the credentials.

Thanks!

Before you knock down this developer’s rating, maybe you could describe WHAT’S not working here, so someone can help you.

Did you try the support page?

That is very weird!

First, try going into Settings > Permalinks. (When you LOAD this page, it rebuilds the permalink settings.) See if that fixes it, by chance.

Now, try changing back to Default permalinks (no URL rewriting happens here). Can you see the same pages this way? (Of course, you cannot call them with those URLs – none will work. But you could try clicking on the page links below, which should adjust to the default URL structure.)

I assume that this last technique will give you no 404s. But at least it gives you a tiny bit more data. Then, change the Permalinks back to the way they were.

Now, since this is a weird situation, I would try disabling all the plugins, and see if the problem is still there. If it is fixed, then, go to Recently Active plugins, and turn them back on one by one. You will find the plugin that is causing some problem (who knows why?). If not, then that is not the issue.

You could also look at the error logs for the site (from your hosting control panel, often), to see if you are getting an error and what kind, with the 404.

Now, you get into weirdness of rewrite rules—maybe *something* is weird. You could try using https://www.ads-software.com/extend/plugins/rewrite-rules-inspector/ … this gets pretty advanced, so it might be too advanced to do alone, but it makes it less difficult to understand.

It is not possible that activating a theme would publish your site, really.

When you install WordPress, it is “live” already, with the default theme.

I think what you want, is a Coming Soon plugin, so you must be logged in to see the work on the site. Then you can turn it off when you are ready: https://www.ads-software.com/extend/plugins/ultimate-coming-soon-page/

Install it, then go Settings > Coming Soon, and turn it on, and save. (Add settings if you want.)

I have the same issue.

Hmmm… I think at this point, Google fonts should work on all modern browsers. Google fonts is using @font-face, just with a remote call to Google. My take—if your server can reach Google.com, you should be fine.

Maybe you should go back. If it was working for you?

Heck, Seth Godin’s been running his extremely famous blog on the out-of-date TypePad hosting system for years.

That’s right. When you say “page,” I think you mean “the actual physical web page”, but in WordPress, “page” has a specific meaning, as a type of data.

Types include:
– page
– post
– archive (for category, date, author, etc.)

You just want 3 category archive pages. It’s easy. In fact, from the Appearance > Menu generator, you can create links to specific post categories.

Well, over time, you might see changes because Google is going to see wordpress.com as a much more prestigious domain than your .info domain (or new .com domain).

But what WordPress is almost certainly doing is making 301 redirects to your new site, and what that says to Google is, “treat this as the same site.” So, in the short term–a few days, a few weeks? — you’d think that Google didn’t know about the new domain, so that was why I was wondering about that.

90% sure is dramatic. I am hoping that over time, it would bump up again. But this is really more of a question for an SEO forum…

I don’t know why that is — but I think there’s a better way to do it anyway — to set up a Virtual Host for each project.

This explanation looks good: https://sawmac.com/xampp/virtualhosts/

The only thing I didn’t see him mention, is that you need to make sure that in the main Apache config file, httpdd.conf, you need to make sure that the include of httpd-vhosts.conf is not commented out. (I think it is, by default).

Here’s another post: https://www.tildemark.com/setting-up-virtual-hosts-with-xampp-running-on-windows-xp/

What I do, is I have a completely standard format that uses a .local extension for my local sites. So if my customer’s site is mydomain.com, I will setup mydomain.local on my local site. You can “fool” your local site to think any domain is local, and then you have a cleaner way of working, IMHO.

This way, it’s a very simple copy-and-paste operation to set up new virtual hosts, once I have set up the first one.

Can you be more specific?

You want to create 3 pages (for example), and have each one *also* output the content of a different post?

It makes me curious why you want this? If you can explain what you’re trying to do with it, maybe I could give you a better suggestion of what to do.

How do you know what the relevant category is for a particular post? (I assume you mean post and not page actually, because normally pages don’t have categories.)

Keep in mind, that a post can have more than 1 category associated with it. Would you want it to list all the posts associated with ANY category associated with that post?