The Newspaper Theme License Key is NOT REGISTERED on this website” error

What the actual hell is going on in here? I get a “The Newspaper Theme License Key is NOT REGISTERED on this website” on my website’s desktop version (everything okay on its AMP version) when I have the theme registered (I paid for it).

The website is https://handthatfeedshq.com/
Everything is okay in the backend however I’ve had someone say it is clearly an error on your side (and something to do with JSON).

I’d very much appreciate it if this error – it can only be an error – be solved quickly as the website is dramatically losing traffic thanks to your mistake.

If that error is not solved within this day, I’ll stop using your theme and move on to another. I can’t have my website breaking from an error that doesn’t make any sense whatsoever, much less when I’ve spent money to have it working stable.

Hoping for a quick reply and fix this error.

Happened to me as well. I went in and reset the Registration Key and then had to put in my registration code again to reactivate. Cleared the cache and everything is back. But yes, it was a big pain!

happenning to my site as well. WTF is this f*cking message. how can this f*cking happen. cant believe it!!!!!

I went in and reset the Registration Key and then had to put in my registration code again to reactivate.

I reset the registration and cleared cache but I still have this big red UNREGISTERED thing flashing on my backend. Very upsetting. I see some of you got your websites online. I don’t know what else to do with mine (theneedling.com).

did u clear your browser cache pal? try incognito mode

Cache was cleared and yeah, did try incognito mode too.

However, it was @yvrmark’s tip that helped fix something that shouldn’t even happen in the first place.

@Calin This is an issue that should never happen to begin with. How can we even know if it’ll happen again and with which frequency? This shouldn’t be the type of problem we’d have to deal with, especially when we’ve already paid for the theme, to begin with.

Well, the issue sure was solved but not thanks to tagdiv’s speed…

+1 for midorin:

This is an issue that should never happen to begin with. How can we even know if it’ll happen again and with which frequency? This shouldn’t be the type of problem we’d have to deal with, especially when we’ve already paid for the theme, to begin with.

It is first time that I see in WordPress community so blatant defacing of a site. If the key is invalid, then worst what should happen is that theme should show up as unregistered in backend and user losing some features, not defacing a site.

How do I reset the registration please?

Hi there, where do you reset the registration please?

How do I reset the registration key please?

You have sold 150,000units x $ 59 = $ 8,850,000 n and do you do this? Evil born, scammers

@ClaireBullivant if you purchased through themeforest, you’ll see the key on the “support” section of the theme’s page https://themeforest.net/item/newspaper/5489609/support.

At the bottom should be your reset registration key. Hope this helps!

@player1 this is pathetic, to say the least. Like @jkp said, defacing a website and making it seem like I have a fraudulent website to all my readers is beyond a “mild inconvenience”, it’s spitting on our faces and completely undermining our hard work with our respective websites (not to mention the fact that we PAID for the theme). This theme was chosen by us for its practicability, perhaps because it looks good or works well on mobile… It was supposed to save us time.

I sure am window shopping for a new theme after this blunder. The uncertainty that tagdiv has put around this theme makes me have to worry about something I shouldn’t – we all shouldn’t – have to worry about.

Instead of making updates to “pretty” the theme up – some unnecessary -, what about making sure something like this doesn’t happen anymore? Or that this only happens for those that are using a pirated version of the theme?
It’s beyond anything normal to have to pay for something and be called a “thief”.

Certainly the first and last time.

After hours of trial and error, I finally got my website back up by deactivating the Newspaper 11 theme and reactivating my old 8.7 Newspaper theme. Relieved to have the website back up.

No matter the coding/API/whatever led to this nightmare, there really isn’t any good excuse for allowing that screen alleging that we all pirated your theme to stay up. There really wasn’t anyone in the last 10 hours who could have at least changed it to a generic error page? That’s ridiculous.

@Bettina If only apologizing would bring back “trust” that is incredibly hard to earn…

For my website that brings in people every day – it has daily news articles and seasonal features – even 1 hour offline already does massive damage to the website (reputation and revenue-wise). I was lucky to find that issue almost as it happened so the damage was only a couple of minutes.

Worse yet when people accessing said website come across a message claiming that I’m a thief <- this will go down as the most ridiculous thing a website dev has ever made.

There is no good amount of copy-paste “apologies” or quick fixes that can solve the mess you guys made to not only mine, but everyone’s hard work and money – you can see how many people were affected by checking this forum. Can’t imagine the people that were worried sick thinking their website was hacked and didn’t use the forums to report this issue because they are not confident writing in English, for example.

The best tagdiv can do is actually follow up their words with meaningful actions that actually reflect your apology for this mess.
Make sure that “Newspaper” theme is secure and unbloathed, without ridiculous errors like this popping up out of nowhere and that can actually match the claims you guys make about this theme being the “best”.

As people that actually paid for this theme when we could have pirated it, you owe us that much. Stability. No worries. Quality.