I sent you an email.

As soon as I posted it, I tried to play with sharing options, as the error was close to the share buttons and sure enought, it was them that were causing the issue.

At the moment, I can’t have sharing turned on (only the like button works with no issues).

I sent you an email with login details.

Hi Simion,

The theme is not working correctly. It is being displayed for a few seconds, when I change the theme layout. Then it reverts back to a responsive theme.

Right now, it is back to the responsive layout with no way of triggering the mobile theme. As I said, I can give you permissions for you to check it if you are interested. 🙁

Hi I tried it right now. Followed each step of the tutorial + deactivated all non-theme related plugins. Once the cache is turned on, the mobile version is not displayed.

Also tried reinstalling the mobile version with no success.

Hi Simion,

Here is the link to the website: http://www.techbyte.sk. If you want to have a look at the theme from the inside, please let me know. This issue is very weird. We would love to use the mobile theme plugin, as it just makes more sense (design, and function-wise).

Thanks in advance,
Lukas

Hi Simion,

The code you sent does not need to be implemented, as WP Super Cache already has the code in it: https://puu.sh/xPLZH/33145683f8.png

As I said, I have followed the instructions, thus I am using WP Super cache.

So I pretty much singled out the problem: Its the cache. Even though, I set it up correctly (double checked with our admin). When I log in on a mobile device to admin (no cache), the correct version is served. As soon as I log out, the reponsive version is served :-/

Hey Andrei,

That’s ok. I was more cuirous than anything else. Thank you for your input 🙂

Is tagDiv thinking about enabling us to turn on/off ads, perhaps using shortcodes or something like that? That would be really useful.

I haven’t managed to fix it. Works great on my other website though, so perhaps something with server settings? I am not sure 🙁

Hi Emil,

I will give it a go. Just before I do, however, do you plan to update the theme anytime soon? If yes, that I would prefer to wait.

Sure Chris, but I wouldn’t defend the fact that update works well when so many people had problems. It is beyond me why their quality control is so bad when so many people bought the theme. There must be an element of *if we f**k this up, people aren’t going to be impressed* which was what happened not only to me but to many.

I would wait if I was you. I tried updating 1.4 to 1.7 yesterday and it didn’t go according to plan. There are some issues that the devs are aware of. So stay frosty and wait for 1.8 I suppose 🙂

Hi,

Yes, I have downloaded and then redownloaded the latest theme pack, tried using newsmag as a name for the theme, tried using our typical folder name, even a child theme, but nothing helped.

When I downgraded back to 1.4, everything was back in normal.

I had to revert back to v1.4 which works great, but i’ve spent 3 hours trying to work it out. Needless to say, I am quite disappointed in how the update process doesn’t work :-/

Hi Alin,

Our server admin checked it and the problem stems from the request itself:

http://fonts.googleapis.com/css?family=Roboto+Condensed:400italic,700italic,700,400|Open+Sans:400italic,600italic,700italic,400,700,600&subset=latin,latin-ext?ver=1.4

There is ?ver=1.4 at the end. If you delete it, it starts to work. When you leave it added, Google responds with 400 bad request.

That’s one way of doing it, however I would prefer everything to run as it should. We shouldn’t have to go back to v1.4 if the newest is 1.5 and the creators of the theme say it should work. I’ll wait for someone from tagDiv to get back to us on this one.

I am reluctant to update the theme now. Why does the Visual Composer use so much more memory? The whole changing of VC element names or running an SQL command isn’t something I want to do, because if it goes south, I don’t want to be left with a non-working web :-/

Hi Lucian,

In further testing and tweaking, I found that the solution I mentioned above doesn’t work well for ads that are on the top (aligned to the right or left). It would be super cool if we could simply turn them off, when we need to, i.e. when someone pays for an article.

Thanks! 🙂
Lukas

In the changelog it says this:

– Rename the short codes via SQL

I’ve got a question about that SQL thing. Is it mandatory or can we skip it?

You are my heroes guys ^^

Hi Lucian,

Thanks for the update. Can’t wait for the fix! 🙂

Lukas