Randy Calvert

Instead of having all of the files under /board/ you would move everything to /. Once there, that will have all the pages, databases, etc all show up correctly. By default, forums would change to /forums/ path instead of /board/. It's easy to edit that however. If you want it to be /board/, from the AdminCP, just search for "Customize Friendly URLs". Search for any mentions of forums/ and change it to board/. (There are 2-3, so it's a simple quick edit.)

It was about an hour or so for me.

From what was said earlier, the menu and footer are not planned for the main IPB release. It's them tweeking the default theme for their own site needs.

In that case, it might require a support ticket for one of the IPB team to take a look at your instance and get you straightened out.

In your conf_global.php do you have the correct path specified? If you right click on broken image, and copy the image location… what does it show for the image path? Is it the old URL or the new one?

Technically you can use any other Russian CDN in front of Wasabi and do the same thing. It would be on that CDN provider if they're providing a SSL cert or allowing you to use Lets Encrypt, etc. CF was suggested and defaulted here because it's free for both the CDN as well as the certificate. You could use any other provider you like however we obviously cannot comment on costs, availability, etc.

You don't need to use Wasabi's SSL. You don't need a custom certificate. You should be using CLOUDFLARE to secure traffic. it has it's own wildcard certificate that is used that will cover anything.yourdomain.com. The request flow should be USER -> cdn.yourdomain.com (CLOUDFLARE) -> cdn.yourdomain.com.wasabisys.com (WASABI) -> USER Create cdn.yourdomain.com within CF's DNS interface. It should be a CNAME pointing to cdn.youdomdomain.com.s3.wasabisys.com (or whatever CNAME you have from Wasabi). You need to make sure the Proxied status is set to Proxy meaning the cloud is orange not grey. You also need to make sure your CF SSL certificate is not set to Strict mode. Go to the SSL/TLS section. You'll see options for "Off", "Flexible", "Full", and "Full (Strict)". Make sure "Full" is selected and not Strict.

If you have an older version installed, IPS is not going to FORCE you to upgrade. They may not be able to provide support if you’re not running the latest version, but as long as things are just working they don’t require it. With that said, they don’t provide old random versions to download and install. So you would not be able to download 4.2.x or 4.4.x and install it simply because you want to run an older version. (You would not want to anyway due to several security fixes that are included in subsequent releases.)

But again, why? If you want to customize your stuff… do it. If you want to share whatever changes you make, put it in the marketplace. You’re making the assumption that changes that someone is making warrant being included as a default change.

For those customers that are self hosted, you have full access to the source code. You can edit if you like. There is also documentation on how to create applications or plugins so that you don’t have to edit the source files and simply extend them instead. It does not make sense for customers to be able to edit IPS’ source code for everyone else. I frankly don’t trust anyone else to make changes that might compromise my site’s security or performance. Those developers I do trust, I use applications available in the marketplace or hire them to custom develop something for me.

IPS\Db\Exception: Too many connections (1040) If this is a server you have root level access to and you're server is not maxing CPU/memory usage, you can increase the limit. https://ubiq.co/database-blog/how-to-increase-max-connections-in-mysql/ The above URL has a mySQL command you can run to temporarily increase the limit, and editing the .my.cnf file will be the permanent fix. In terms of your plan to move to a new server... BEFORE you move, make sure the new server is fully up to date. Get everything installed/configured correctly. Make sure the new server has all of the dependancies you need. You can use the following script to make sure your new server has all of the required components installed. Once the new server is ready, copy the entire file structure (typically under /public_html) to the new server. Export your database from the old host and import it. Make sure you have a mySQL user created and that it has permission to access the new database. Then edit conf_global.php to change any system paths or database username/passwords. Once that's done, you might want to test everything before pointing live users to the new server. The following URL has info on how to edit your OS's host file to manually point YOUR DNS to the new server without effecting anyone else: https://kb.leaseweb.com/products/hosting/web-hosting/adding-a-website-to-hosts-file-and-testing-it Finally once tested, remove the host file entry and point live DNS to the new host. Good luck!

From what Matt posted earlier, yes.

FPM (FastCGI Process Manager) is still a CGI mode. Per the instructions, you cannot use CGI mode. So that means those methods above would not be appropriate. I have not tried this myself, but my guess is you need to run PHP as a CLI. If you're using cPanel, I'd assume this would be appropriate for you: https://docs.cpanel.net/ea4/php/easyapache4-and-the-ea-php-cli-package/ https://docs.cpanel.net/ea4/php/introduction-to-php/ In looking at the docs, I noticed CLI has a different path than the normal CGI. So you might need to account for that also.

Hey guys! We've been making use of the ModCP across our site as a way to manage actions taken by our moderators. Having spent more time in the area, I have a few suggestions I was hoping you might consider for a future version: Once a report is made, there is no way to interact with the person that reported the content or to interact with the person being reported (other than to warn them). At the bottom of the report currently is two tabs, one for the content from the person reporting, and another for moderator content. Allowing moderators to reply to the first tab if we wanted to interact with the person reporting would be helpful. (Collect more info, get a better understanding of what the intent was, etc.) -- Since members don't have access to the moderator CP, maybe from the member perspective it's a PM? Create an additional tab with the ability to interact with the person being reported. There are cases we don't want to warn someone, but maybe a gentle nudge first can help de-escalate a situation. These areas would be AWESOME to include the new stock replies feature. Where we can pick from a few canned replies and customize them as needed. There is no easy ways to find reports involving specific members. For example, in the reports section... it would be cool to be able to find reports involving (started or about) a member. Today you can only filter by report status. The AdminCP shows warnings issued. Could we also see reports and if a warning was tied to a report show that relation? Could we have a way of editing a warning? Once a warning is issued, if a decision is made to reduce the warning points for example, the only way to do this is to revoke the warning and reissue it... this means the member must re-accept the warning which causes confusion. It would be helpful to be able to edit a warning versus only being able to revoke it. This would help make our moderator's workflows much easier and make tracking issues much more straight forward. There are times I've had to go look up something that happened six months ago and have trouble putting a timeline together fully of what happened. 🙂

It’s not about being hard to do. It used to be in early versions of IPB and was removed. I believe the reasoning was to simplify the user interface, especially on mobile devices. I would not hold my breath on this happening. If this is one of those oddball features that is super important to you, instructions exist on how to add it yourself.

I’m not IPS… I don’t speak for them and I don’t work for them. So just a couple of thoughts of my own. There is a difference between “listening” to feedback and just doing whatever is suggested. There are members in my own community that make suggestions… some are able to be accommodated and others not. There are times that some are pretty vocal… but their request does not fit with the long term strategy for the community. I see the same thing here. There is a bigger vision that IPS is working towards. That means that it is not possible to always accommodate requests. In terms of a “landslide” poll, it had a total of around 50 participants out of literally thousands of customers. I don’t think that’s a fair representation of the entire customer base. I would venture a guess that if literally all customers were to be asked that a majority would have no clue or not care. With that said, there is always going to be some group of people where it’s critically important. For ANY feature or change, it’s made out to be THE defining feature of their community. The fact that instructions have been provided to accommodate individuals that felt so strongly about it shows they indeed listen. Just because it makes sense for your community does not mean it makes sense as a default feature. But the awesome thing about the way the system is built is that if you don’t like it, changing it to the way you want it is not overly complex or hard especially when it’s spelled out how to do it. I’ve been an IPS customer for over a decade and I can say they approach development the same as they always have which is pretty similar to Apple. It’s to look at the big picture and figure out what customers actually need. Sometimes customers know… sometimes they don’t. If Apple simply built what “the majority” wanted we would not have had the revolution in the mobile market that we did. The question will be if IPS can successfully read the tea leaves and figure out what is important before we actually know it’s important.

Awesome! Glad you got it squared away!

I use Cloudflare's WAF and created a rule to block traffic from Russia and China as a good amount of the junk traffic we received from there. (We don't have any real legitimate traffic from there.) It might be worth considering blocking those areas higher up in the stack either in .htaccess, in your firewall, etc. By the way... if you use .htaccess, you won't be able to just list a country, but there are some good resources that will let you pick a country and it will give you the IP ranges and generate the .htaccess code for you to block the IPs used in those countries. Check out: https://www.countryipblocks.net/acl.php

We need more information. What device and browser are you using? If you're using a supported device/browser, have you enabled push notifications by going to Notifications > Notification Settings > Push and clicked "Setup this browser"?

You can add robot rules pretty easily... from the ACP: Search for "Search Engine Optimization" Click "Meta Tags". Enter the base URL of the database with a wildcard (/articles/* for example) Click the blue "+Add" button. Under the "Meta Tag Name" option, choose "Robots". Under the "Content" option, enter "noindex" Save your changes. By using a wildcard in the database URL, it will cover all database records under it. This would be harder to do for forums and clubs as they don't have a common URL structure. Databases should work however.

Have you cleared your system cache? From the ACP, click on Support. Once the page finishes loading fully, click the button on the right to clear the system cache.

Inside of your conf_global.php will be: 'base_url' => 'https://www.site.ru/', Change this to: 'base_url' => 'https://site.ru/', Basically just remove the www reference. 🙂

When creating a table, unless otherwise hard coded into the query to specify InnoDB, it will use the server's default format. CREATE TABLE t1 (a INT, b CHAR (20), PRIMARY KEY (a)) ENGINE=InnoDB; It's not generally a good idea for app developers to be setting the engine as there are reasons a sever is set with a specific default. I would personally recommend setting your server to just default all new table creations to use InnoDB. This can be done by editing your /etc/my.cnf file to add: default-storage-engine=InnoDB under your [mysqld] section.

How about this…. go ahead and write a decent sized software application first and then come back and tell us how it goes after a year. It’s real easy to sit in the wings passing judgement on things you have no clue about. EVERY single software application that exists has maintenance releases. I assume you also will never have used an eraser or the delete key before because you type everything perfectly the first time.

Really?? You gotta be kidding me. That is the most outlandish statement I’ve read in a while. Every single major software company issues security updates. What is not known today may be known tomorrow and need to be fixed.