Bug Option for Likes comes back after already liking post

[Fillip H.]

Well I just tried it again on my localhost and I had no issues with it even when it went beyond the cutoff point.

I tried to re-upload the files using the FTP account you created a while ago, but I seem to be unable to upload files. They just get stuck at retrying later.

 

[s3ponline]

Well I just tried it again on my localhost and I had no issues with it even when it went beyond the cutoff point.

I tried to re-upload the files using the FTP account you created a while ago, but I seem to be unable to upload files. They just get stuck at retrying later.

I apologize. It should be fixed now.

It may have happened while we change all our stuff around PHP, MYSQL, etc.

Which btw, killed some bugs if anyone else is wondering. I would let people know what versions they should be running to get the best out your products

 

[s3ponline]

BTW, you might actually have to view the issues from an older account.

 

[Fillip H.]

I temporarily set the cut-off point to 1, registered a new account in a different browser (Fillip H.) and tried to Like a post.

Exclusivity + un-liking worked perfectly for both the displayed user and the "cut off" user.

 

[s3ponline]

I temporarily set the cut-off point to 1, registered a new account in a different browser (Fillip H.) and tried to Like a post.

Exclusivity + un-liking worked perfectly for both the displayed user and the "cut off" user.

The issue works perfectly for NEW likes.

It's about things that I have already liked in the past that have gone through the "cut off"

That's why I think you'll have to access my personal account to see the issue

 

[Fillip H.]

But "old likes" use the exact same code

 

[s3ponline]

 

[Fillip H.]

Yeah, but if that happened during the brief period of time when exclusivity wasn't working then that would make sense. There's no way to change that now, though

 

[s3ponline]

Yeah, but if that happened during the brief period of time when exclusivity wasn't working then that would make sense. There's no way to change that now, though

The date is on there. August 31st. Or do you mean before it was a feature?

 

[Fillip H.]

I mean before it was a feature, or during the time(s) when the feature was broken

 

[s3ponline]

Well alrighty. I guess I can live with it. Let’s see how it goes. Hopefully that’s the last bit for the future on.

Thanks for solving the issues.

 

[Fillip H.]

I hope so too xD

Thanks for your patience and assistance

 

[s3ponline]

There’s an issue now where if people use Thank/Like the custom button can’t be used.

Likewise, if the custom button is used by another member, I can’t like/thank.

 

[Fillip H.]

You have a couple of issues on your forum at the moment.

When I tried to log in to your AdminCP by just going to pnation.com/admincp I was greeted by a list of files; somehow the DirectoryIndex directive has broke.

I went to check out your button setup, and found that one of the APTL templates had been customised (which may be the cause of this issue). When I tried to click View Highlighted Changes I got this message:
Fatal error: Call to undefined function gzcompress() in /var/www/includes/class_diff.php on line 170

I've been unable to replicate this issue using the exact same button layout you're using, so it may just be that template that's causing it.

 

[s3ponline]

You have a couple of issues on your forum at the moment.

When I tried to log in to your AdminCP by just going to pnation.com/admincp I was greeted by a list of files; somehow the DirectoryIndex directive has broke.

I went to check out your button setup, and found that one of the APTL templates had been customised (which may be the cause of this issue). When I tried to click View Highlighted Changes I got this message:
Fatal error: Call to undefined function gzcompress() in /var/www/includes/class_diff.php on line 170

I've been unable to replicate this issue using the exact same button layout you're using, so it may just be that template that's causing it.

Ah, fixed the issue and it fixed the other issue.

Thanks for the tip

Spoke too soon. Going to open up a new ticket.