Jump to content

Community

DawPi

+Clients
  • Content Count

    6,778
  • Joined

  • Last visited

  • Days Won

    7

 Content Type 

Profiles

Downloads

IPS4 Documentation

IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Forums

Posts posted by DawPi


  1. 8 hours ago, Midnight Modding said:

    Shouldn't there be a way to reset password within the upgrade routine login? For the second time I just ended up in a situation where I forgot my pw and the site wouldn't load, due to errors from having the new files up, so the only place I could have a page load was the login for upgrade pages.

    Quote

    In 4.3 and higher, when logging into the upgrader, you will need to use an email address / display name and password using the standard, internal login handler. If you normally use a different method for logging into your community, you can bypass logging into the upgrader by adding this line to constants.php:

    
    define( 'BYPASS_UPGRADER_LOGIN', TRUE );

     

     

    8 hours ago, Midnight Modding said:

    Also, another problem with that site is bots kept spamming the contact us link... and there was no way to disable the feature, from what I could tell. I haven't even used the site in years because it was impossible to deal with.

    2019-04-23_09-48-12.thumb.png.d1f9104ba0b681bdf8eea77b82b8a806.png


  2. On 11/8/2018 at 5:14 PM, Cyboman said:

    Google shouldn't crawl my pages and detect a linking overdose. An option would be useful to restrict links per post, links per author, and links per page.
    If you have too many keywords linked, and many keywords are used by the poster, this sometimes results in in a huge amount of links per page. 

     

     

     

     

     

     

     

     

     

    What's New in Version 4.0.0  

    • fixed bug related to alt/a etc. html tags,
    • added option to limit how many times one phraze should be parsed in each post.

  3. 4 minutes ago, Kenneth Baker said:

    Hi Dawpi 

    Could you advise with what command to run exactly? i get the same error as Matk , theres allot of different solutions on that page and i dont know what to do

    The best for you will be this advice:

    Quote

    Solution 2: Remove ONLY_FULL_GROUP_BY from phpmyadmin

    • Open phpmyadmin & select localhost
    • Click on menu Variables & scroll down for sql mode
    • Click on edit button to change the values & remove ONLY_FULL_GROUP_BY & click on save. enter image description here

     

×
×
  • Create New...