Presslabs

Hello @snurk,

I believe you’re using the default template file for your top? If not you can simply edit your custom version as follows.

If you’re using the default template you need copy the widget.blade.php file, in the same directory and name it custom.blade.php.

Now, edit this custom.blade.php file and replace all “{{” occurences with “{!!” as well as “}}” with “!!}” and let me know if this works.

This is the file I’m talking about: https://github.com/presslabs/toplytics/blob/master/src/resources/views/frontend/widget.blade.php

Best regards,
~Cristian – Presslabs Support Team

No, for sure you don’t have to do any changes in the DB, because the actual post title has changed already. Please allow us more time to get this investigated, as it shouldn’t happen, even if you were using the so-called “long” dash.

Thanks for your patience.
Pedro/Presslabs Support Team

Hi @snurk,

The issue comes from the type of “-” code you have used in that post title.

What I suggest as a quick fix in this case is:
1. Update that post title and replace the “-” with a typed “-” symbol, from your keyboard. There is a very high chance that the character used now was generated by a rich text editor such as MS Word or similar
2. Clear the cache of that post, if you have it enabled
3. Fetch again the data from Toplytics, by going to settings
4. Refresh the page and let us know how it goes

Let us know if it works this way!

Pedro/Presslabs Support Team

P.S. Additional question: how do you see it in your Google Analytics? Is it displayed properly?
P.P.S I have opened up an issue for us to investigate further: https://github.com/presslabs/toplytics/issues/143

Many thanks for the review @snurk!

In case you have any other issues, please write again on the Support Forum. Or if you have any suggestions, please add them here:

https://github.com/presslabs/toplytics/issues

Best regards,
Presslabs Team

I’m very glad that everything works smoothly now! And thanks for the review ??

No. the issue is the PHP version you are running. Please note that the new version of Toplytics requires at least PHP 7.0 in order to work, therefore you have to upgrade it in order for the plugin to work.

Please note that both PHP 5.6 and 7.0 are end of life, therefore I suggest you to upgrade immediately to at least PHP 7.1, in order to be protected for security issues that might arise with these older versions of PHP.

https://php.net/supported-versions.php

Unfortunately, until you upgrade to a newer version of PHP we won’t be able to help you furhter ??

Best regards,
Pedro/Presslabs

• This reply was modified 6 years, 1 month ago by Presslabs.

Can you please tell us which PHP version are you using as well as the WordPress version that you currently have?

Ah, you are right, that archive contains the whole repo. Please use this one instead:

https://dl.presslabs.net/toplytics-v4.0.0.zip

Let us know how it goes now!

Best regards,
Pedro/Presslabs team

Hello @snurk,

This might indeed happen and that’s why we have completely rewritten the plugin. However, we bumped into some issues when trying to push the updated version in the WordPress repository (most probably due to the GA API files size).

As a conclusion, can you please try to manually update the plugin with the one found on our GitHub repo, here:

https://github.com/presslabs/toplytics/releases

Just grab the ZIP file from our latest release and install it in WordPress after removing the version you have now (probably 3.2).

Please let us know if you still have issues with this version!

Best regards,
Pedro/Presslabs team

Well, that’s the whole beauty of the gitignore! You can alter the gitignore file in order to fit it to your needs. For example, I don’t see any reason why you’d have /uploads/ or /upgrade/ or /backups/ in git! The main folders that you’d probably be interested in storing in git are: /plugins/, /themes/ and /languages/. Maybe some other specific plugin folders, depending on what you’re using, but that’s about it.

Getting back to your issue:

Yeah, but Gitium generates a wp-content folder that misses some files and subfolders.

Add the files you need on top of the wp-content folder generated by Gitium, then add them to gitignore, so that they won’t be committed in the repo, but you’ll have them for your local MAMP setup. If I’m not mistaken these files will anyway be added by MAMP, so you’ll only need to ensure you’re not committing files that should not get committed to a Git repo (such as backups, logs, etc.).

This is something I haven’t tested as I haven’t used MAMP for quite some time now. Would it work if you cloned the repo directly in the MAMP setup? depending on the structure you have with your repo, this would probably be the easiest way. Then you test all changes on MAMP and only commit & push when happy with the result.

Would something like this work?

Pedro/Presslabs Support Team

Hi @maurolopes and thanks for this question.

There are many ways you can achieve this, I’ll share with you how we do it.

We’re using for the site repos where Gitium is used, the file structure from here:

https://github.com/presslabs/gitium-base

You can simply clone it, then copy the file structure, then add your theme and plugin files on top, then push everything to the repo you’ll be using with Gitium.

It comes with a predefined setup for a local environment that works with Vagrant & Vbox. All you have to do is to import a DB dump, some images and you can find more details about how you can achieve that on this article from our documentation. In this way you’ll be able to do changes and check them locally before getting them pushed to the repo.

Please let us know if this works as expected for you.

Best regards,
Pedro/Presslabs team

Hello and thanks for writing to us.

To my knowledge, we haven’t encountered this kind of behavior until now. And from your message, I understand that your setup with Gitium works fine on InMotionHosting, but doesn’t work on Cloudways, which makes me think that it’s somehow host related.

Do you have any kind of logs available that we could check in order to understand what is going on? Even if we can assume that it’s a permission issue, some details/logs would certainly speed the debugging up. Alternatively, would it be possible to give us some kind of access to the CloudWays setup in order to have a look as well?

Looking forward to getting your reply!
Pedro Dobrescu
Presslabs Support Team

Hello @boulderpoet

We are testing this functionality right now for our new version 4 of the plugin.

If you want to help test the BETA we can send it over via email if you hit us up on support[at]presslabs.com.

Best regards,
~Presslabs Team

Hello @egocefalo,

Thank you for your kind feedback.

A complete rewrite of Toplytics is coming very soon. ATM it’s in closed BETA but you can give it a try or have a look at it here: https://github.com/PressLabs/toplytics/tree/toplytics_v4

Best,
~Presslabs Team