Gabriel Torres

+1

Hi,

This is an old issue for us. We can limit signatures only by number of lines, but this is insufficient for us, as some users are abusing this and posting really long lines, so their signatures are huge.

It would make more send for us to limit the number of characters, not lines.

Another suggestion for signatures would be that links to contents such as topics wouldn't be converted to their "embedded" version, but kept a normal URL link. Currently we use a custom plugin to fix this, and it would be nice if this was a core feature.

Thanks.

@Daniel F Jeez! Thanks! I will take a closer look and fix the boo-boo I've done to our database.

@Marc Stridgen @Daniel F Nevermind, I found the culprit... In the past I manually deleted some members using a MySQL query, and I haven't deleted the corresponding records in the core_follow table. Therefore, the issue is entirely my fault. I no longer will delete users using queries, as this breaks things up... Thanks!

Hi,

This is regarding the Pages (cms) app. We have a couple of databases with the review option enabled. Now, when I try to answer a review, at the front-end everything seems to be working, but the answer isn't saved in the database (I know because the review_author_response row in the cms_database_reviews is NULL for the review I replied to).

I tried with thee default, unmodified theme, to the same result.

It was working before when we were running an older version of IPS, but this issue only came to my attention today, when I tried to reply to a customer.

Thanks!

7 hours ago, Daniel F said:

Is this also happening with your default thme?

As I explained in my post, this is not a theme issue. The error is thrown when one of the followers simply don't exist. The member_id is there in the core_follow table, but the member with that ID doesn't exist at the core_members table. Deleting this rogue records solved the issue for me.

@Marc Stridgen As I mentioned, I deleted the offending records. My best bet is that a routine in charge of deleting users is not deleting the corresponding records in the core_follow table. I would suggest testing this by getting a test user, making it follow another user, then make the test user request his account to be deleted, approve this deletion and checking if the record in core_follow table was deleted as it should.

@Vasile Rogoz @Marc Stridgen

Today I saw this very same error in our system log. The OP failed to provide more detailed info. This error shows up when trying to see the full list of followers from a user. E.g.:

https://invisioncommunity.com/profile/536186-marc-stridgen/followers

Here, this error was being thrown when trying to see the follower list of a specific user. All other users the follower list displayed just fine, without throwing an error. So I knew it had to be an issue with that single user.

Upon further investigation, I discovered that there was one row in the core_follow table that was pointing to a user that no longer existed. Deleting that specific row solved the issue. In fact, I found a total of 10 rows (out of 460,000) with the same issue. Deleted them all with:

DELETE FROM core_follow WHERE follow_member_id NOT IN (SELECT member_id FROM core_members);

Now, why this inconsistency happened? I have no clue. Maybe this is a bug caused by a third-party app, maybe it is a core bug, caused by a routine that should have deleted the corresponding rows at core_follow when the user was deleted (maybe when users request their account to be deleted?). I have no further info for you at this time, but you ought to test this further.

I hope I have helped.

Cheers!

We also need to swap the location of the <br> tag, so we don't end up with two <br> tags when no navigation bar is present.

On line 12

Where:

{{endif}}
<br>

Should be:

<br>
{{endif}}

Hi,

If you take a closer look at the user's all followers list, you will notice two things.

Please consider this link as a reference: https://invisioncommunity.com/profile/87228-andyf/followers/

1. The backgroup is gray. IMHO, it should be white.

core > front > profile > allFollowers

Where: 

<ul class='ipsDataList'>

Should be:

<ul class='ipsDataList ipsAreaBackground_light'>

2. The top pagination is too close to the <h3> header. More spacing is needed. See:

Where:

<h3 class='ipsType_sectionHead'>

Should be:

<h3 class='ipsType_sectionHead ipsMargin_bottom'>

Just my two cents.

Cheers!

@DawPi

You current approach: simple textarea

Best approach: WYSIWYG editor

5 hours ago, DawPi said:

Better? 🙂

It helps, thanks.

5 hours ago, DawPi said:

Which editor?

The standard WYSIWYG editor from the platform instead of a textarea field.

Cheers.

Hi,

In the cookies policy page (/cookies), e.g. https://invisioncommunity.com/cookies

The header "Third Party Cookies" should be displayed only if the "Third Party Cookie Details" field in the ACP > Terms & Privacy Policy > Cookies page has been filled out.

It doesn't make sense a header with no corresponding text under it.

Just my two cents.

Cheers,

Gabe.

On 7/1/2023 at 5:21 PM, Miss_B said:

A.f.a.i.k. guests and google bots should be treated the same. Doing otherwise can result in a forum being blacklisted from their services.

Not the case here. We can instruct search engines to not index pages without useful content, such as the case of pages that display "you can't access this page"... See that my proposal is to give a hint to search engines to not index profiles that display this kind of message...

@Miss_B I liked the concept of this app. A few questions and ideas.

1. A setting to automatically configure banned users to "no one".

2. When guests can't view the profile, did you set the noindex meta tag, so it gives a hint to Google/Bing that they shouldn't be there?

Cheers.

The only drawback is that this caching will impact in the number of recorded views for each item (topics, articles, and so on), right?

19 hours ago, Daniel F said:

Make sure to also exclude the api directory if you want to use REST / GraphQL

I don't know what "REST / GraphQL" is. Please advise.

Gabe.

Just now, SeNioR- said:

Correct. I forgot to mention there is a problem with changing language and theme. The cache still shows the previous language or theme, but this is a sign that the cache is working.

Not an issue for us here -- we don't allow guests to change themes or language anyway.

Hi,

I was reading at the feature deprecation list the following:

Quote

[Classic] Guest Page Caching
This is a legacy way to cache pages for efficiency. Our platform can now be used with a CDN for guest page serving.

We use CloudFlare. I was wondering whether we need any additional steps for caching guest pages at the CDN level or if any additional configuration is needed. Please advise.

Cheers,

Gabe

29 minutes ago, DawPi said:

Hm, any suggestions about these tags?

Ideally something along the lines of:

Your topic has been moved: <title>

Your topic has been edited: <title>

Your post has been hidden: <title>

Where <title> is the topic's title.

31 minutes ago, DawPi said:

Below the PW content? 🙂

It could be incorporated in the #reason_stuff# tag.

Currently: John Doe moved a topic <title>

Proposal: John Doe moved a topic <title> from <origin> to <destination>

Where <origin> and <destination> are the forums names with links to them.

Thanks for the reply! 🙂

@DawPi

I've just installed your app and I have a few suggestions:

1. Replacement strings (tags) for the title. As it happens, right now all private messages have the same title, which is not the ideal. The user who has three different topics/posts moderated, will receive three messages with the same title and might think they are simply duplicates. Also, in the future, it might be difficult to locate a specific message.

2. For the move action, to add the source and target forums.

3. The content editor could use the Rich Text editor

Thanks!

Hi,

When we move a topic, the following entry is created in the moderation history for that topic:

modlog__action_move

Moved a %s: <a href='%s'>%s</a>

My suggestion is to add to this string the source and target forums. E.g.:

Moved a %s: <a href='%s'>%s</a> from %s to %s

Here in our daily operations, oftentimes we need this information, and it would be great if it were readily available.

Thanks!

@Ryan Ashbrook

4 hours ago, Gabriel Torres said:

The current IPS version has the alert feature. However, our moderators need to manually fill out the required fields every time, which is time-consuming and really annoying.

@Marc Stridgen Addendum: I said PM, but it could be implemented through notifications.

@DawPi Many thanks for pointing me to this app! 🙂

Hi,

Is there a way to send automated PMs upon moderation actions (e.g., when a topic or post is hidden, deleted, moved etc)?

I used to acomplish that with the Automation Rules plugins, but it is no longer supported, so I had to uninstall it.

The current IPS version has the alert feature. However, our moderators need to manually fill out the required fields every time, which is time-consuming and really annoying.

If there is no solution for that, could a member of the staff move this topic to the Feedback forum? Thanks.

Thanks!

@AL B

Also, try:

It works great here for us.