Jump to content

bfarber

Clients
  • Posts

    163,911
  • Joined

  • Days Won

    346

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Invision Community 5 Bug Tracker

Forums

Events

Store

Gallery

Everything posted by bfarber

  1. Sounds like a file permissions issue, or you have a bad .htaccess setup for friendly URL rewriting.
  2. That might explain why I can't reproduce locally in that case.
  3. As I recall (I don't work on that area very much) you have to get approved by Facebook manually and it can be a challenging process. I'm not 100% certain on that off the top of my head though.
  4. The content will remain but be attributed to a "guest" user. This tool was available in 4.3.x as well.
  5. I cannot reproduce with the information provided. Please submit a ticket so we can take a look at your community to determine why this might be occurring.
  6. You're misunderstanding my suggestion. Yeah you definitely don't want to delete each member one by one. I'm suggesting you use the "mass" tools available for managing accounts. Do this: Log in to the AdminCP Visit Members > Groups Click the number next to the "Members" group. You will see a list of members. Then click the link to prune all of the results found as seen in this screenshot Repeat those steps for each group, except for admins which you'll delete one by one because you'll need to preserve your own account (there shouldn't be that many admins so this shouldn't be a problem).
  7. Thanks - I've pushed a change to resolve this concern for 4.5 upon review by the development team.
  8. Generally speaking you should submit a ticket to report bugs - we don't always monitor this forum religiously looking for issues. That said since I did happen across this post I'll make a note to take a look. In the future though, just drop us a support ticket to report things like this. 🙂
  9. If you mouse over the date that displays like "Wednesday at 4:21PM" it shows you the full date and time like "4/15/2020 4:21PM"
  10. If you are not using email validation why do you have accounts pending validation that you want to delete? Those should, in theory, be accounts pending admin validation and you should go through them to either validate or deny the registration.
  11. You could search for all members in a group and then choose to delete all of those users. It would take some time for this to happen via the background tasks but I would strongly discourage you from trying to do this in the database directly (there are tons and tons of tables that would need to be considered). Just search for all users in the "Members" group and choose to delete the results. Repeat for each group except admins, and then delete any admin accounts except yours one by one.
  12. The task runs every 5 minutes and sends however many pending digest emails it can, resuming where it left off on the next run. There is no way to control when the emails are sent - it depends on so many factors it would be hard to even approximate it.
  13. Did you remove Downloads by chance? It seems like you are attempting to view a purchase of a file in Downloads but the templates can't be found.
  14. Facebook changes things on their end practically weekly (at least it feels that way sometimes) so it is challenging to keep the guide up to date.
  15. Based on your existing stats, 1G should be more than enough.
  16. That is correct.
  17. Installing Invision Community for the first time is a fun and exciting process. After all, you're about to launch a new community that is going to thrive and attract members from all over, and you want to make sure you set it up just right to facilitate a painless experience for your visitors. If you're new to Invision Community, however, it can be a little daunting when you think about "ok what now?" immediately after installing the software. Though experience, and researching the analytical data Invision Community installations voluntarily share with us, we identified many common settings that most communities change, and it is easy to see why. In an effort to make Invision Community more approachable to new administrators, we have devised an intuitive "new installation" onboarding process that will help you configure the community just right, and quickly. Upon first logging in to Invision Community after installing the software, administrators are presented with a welcome screen. Welcome to your new Invision Community! You can obviously skip this step by clicking away to another page if you wish, and you won't be bothered again. If you click the "Skip this step" link on the page, you will be sent an email with a link to return to the page in the future should you wish to do so. Continuing into the helpful wizard, you will be presented with a screen like so A helpful guided wizard You'll note that there's an explanation as to why you may wish to configure these settings, as well as guidance for where to find the same options later should you wish. Upon clicking next, you'll see the previous step marked as completed. You can even skip around steps by clicking and expanding on them should you wish to do so. Each step is explained in detail If you reached this page but decide that you have to do something else first, there is a "Remind me later" option at the bottom of the page. Clicking it will allow you to resume whatever else you need to do first, but will helpfully bring you back to this onboarding step at a later time to finish your quick setup. Finally, once you submit the form you will be presented with a confirmation page containing links to several other areas that you may wish to visit to get started. Things like setting up forums and setting up groups are common tasks, so we've consolidated links to those areas on one helpful screen as part of the new quick setup. Confirmation that you're doing great so far! This change is but one small way that we strive to ensure our software is easy to understand and easy to use. The next time you set up a new community, we hope these adjustments make the process smoother for you, allowing you to get the backend work done quickly so you can focus on the real goal - growing your new community.
  18. When you install the software you can specify a prefix, though none is specified by default in recent versions. You would have to open your conf_global.php file and look for the sql_prefix option to see if one is specified. If there is (let's say "ibf_" as we used to default to in the olden days), then the query would need to use "ibf_forums_topics" and "ibf_forums_forums" instead.
  19. Do you have an example URL that you want to embed which doesn't automatically embed?
  20. If you made a new forum (not category) to place them in, you could run the following database query to move your existing orphaned topics to the new forum (make sure you take a full database backup first in case anything goes wrong). update forums_topics set forum_id=X where forum_id not in(select id from forums_forums); Replace 'X' with the new forum id you just created, and add any database table prefix you may have to the two table names.
  21. There is no way to "secure" these files, but the randomized value added to every single filename makes it impossible to simply guess the filenames. As long as you have directory indexes turned off (or an index.html file in the folder to prevent it), I really wouldn't be worried about it.
  22. This is not true. If a user does not have permission to access a page, then a 403 response is correct. It would be far worse to send an error message with a 200 response because then you are telling the visitor (spider) "this page is being delivered correctly and here is its content". Perhaps you can simply not show the links to these pages to guests if you are concerned about them?
  23. The only reason a patch would not show up as available on the other site is because it is already installed. You may have updated to the latest release on that site after the patch was issued.
  24. I'd recommend just ignoring the member history. The same thing happens with our client area, it's not an issue.
  25. Most of the time this is due to mod_security on the server, or a similar "firewall" or security protection.
×
×
  • Create New...