6ichem

After doing some googling I came across this You should check it out

Can you link me any docs or some instructions please? I'm pretty confident I can pull it off if I get some kind of directions where I should look

C++ / C# Wait so there is no way this can be done?

Hi, I'm trying to build something but I need it to use the forum's credentials for users. Per eg use the username/pwd used in the forum to authenticate on my app. How can this be achieved? I can't find anything about it on the API and I can't understand how oauth works exactly. Thanks in advance

Damn I really missed it, I was looking somewhere else. Thank you

Hey, I thought display name was meant to be a username but people are able to register with spaces on their display name. How can I disable that? I've been looking on the adminCP for like an hour now and found nothing about it

Hey, my users are not able to add a profile picture. Everyone is getting an error with code -200 saying "an error occurred when uploading this file" What could this be? Any way to solve it? Thanks

Hi sorry if this isn’t the correct forum but I’m looking for a developer to make me a plugin that allows me to see the income per product on my commerce stats. Thanks

bump?

Hey, there is an option to view sales per product in commerce stats but not income per product which I find to be really odd. Is there any plugins for that or am I missing something on the admin dashboard?

That fixed it thanks a lot!

Good point, I'll try doing it with OAuth (I never used it before). Would it require cors as well? I'm still struggling to fix that...

As the title says it, I moved my forum from root to another folder and now all the icons in the forum look like this: With also a lot of errors in the console that says "Failed to load resource: the server responded with a status of 404 (Not Found)". I changed my forum url on the config_global.php file, am I missing something?

Well there isn't really a point of using OAuth if the information I'm trying to get is basically something public that can be viewed by even guests right?

I'm getting this error when making a get request from my frontend to the IPB api: Access to XMLHttpRequest at 'url' from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. The request works fine when using postman and passing the API as username with no password (like mentioned in the docs) but when doing this with react/axios on the frontend it doesn't seem to work. Is this an issue with IPB? How can it be fixed? I'm no backend pro so any help would be really appreciated. Thanks

Make a separate thread for your issue, it has absolutely nothing to do with this

My server was set up by somebody else and I don't have a specific config file for the domain, it uses the default (mydomainexample.com is my domain I've hid the name for personal reasons). I was told to move my files to /forums instead of root so that I achieve what I'm looking for and I had to enable rewriting URLs which doesn't seem to be working ## # You should look at the following URL's in order to grasp a solid understanding # of Nginx configuration files in order to fully unleash the power of Nginx. # https://www.nginx.com/resources/wiki/start/ # https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/ # https://wiki.debian.org/Nginx/DirectoryStructure # # In most cases, administrators will remove this file from sites-enabled/ and # leave it as reference inside of sites-available where it will continue to be # updated by the nginx packaging team. # # This file will automatically load configuration files provided by other # applications, such as Drupal or Wordpress. These applications will be made # available underneath a path with that package name, such as /drupal8. # # Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples. ## # Default server configuration # server { listen 80 default_server; listen [::]:80 default_server; # SSL configuration # # listen 443 ssl default_server; # listen [::]:443 ssl default_server; # # Note: You should disable gzip for SSL traffic. # See: https://bugs.debian.org/773332 # # Read up on ssl_ciphers to ensure a secure configuration. # See: https://bugs.debian.org/765782 # # Self signed certs generated by the ssl-cert package # Don't use them in a production server! # # include snippets/snakeoil.conf; root /var/www/html; # Add index.php to the list if you are using PHP index index.php index.html index.htm index.nginx-debian.html; server_name _; location / { # First attempt to serve request as file, then # as directory, then fall back to displaying a 404. try_files $uri $uri/ =404; } # pass PHP scripts to FastCGI server # location ~ \.php$ { include snippets/fastcgi-php.conf; # # With php-fpm (or other unix sockets): fastcgi_pass unix:/var/run/php/php7.3-fpm.sock; # # With php-cgi (or other tcp sockets): # fastcgi_pass 127.0.0.1:9000; } # deny access to .htaccess files, if Apache's document root # concurs with nginx's one # #location ~ /\.ht { # deny all; #} } # Virtual Host configuration for example.com # # You can move that to a different file under sites-available/ and symlink that # to sites-enabled/ to enable it. # #server { # listen 80; # listen [::]:80; # # server_name example.com; # # root /var/www/example.com; # index index.html; # # location / { # try_files $uri $uri/ =404; # } #} server { listen 80 ; listen [::]:80 ; # SSL configuration # # listen 443 ssl default_server; # listen [::]:443 ssl default_server; # # Note: You should disable gzip for SSL traffic. # See: https://bugs.debian.org/773332 # # Read up on ssl_ciphers to ensure a secure configuration. # See: https://bugs.debian.org/765782 # # Self signed certs generated by the ssl-cert package # Don't use them in a production server! # # include snippets/snakeoil.conf; root /var/www/html; # Add index.php to the list if you are using PHP index index.php index.html index.htm index.nginx-debian.html; server_name mydomainexample.com www.mydomainexample.com; # managed by Certbot location / { # First attempt to serve request as file, then # as directory, then fall back to displaying a 404. try_files $uri $uri/ =404; } # pass PHP scripts to FastCGI server # location ~ \.php$ { include snippets/fastcgi-php.conf; # # With php-fpm (or other unix sockets): fastcgi_pass unix:/var/run/php/php7.3-fpm.sock; # # With php-cgi (or other tcp sockets): # fastcgi_pass 127.0.0.1:9000; } # deny access to .htaccess files, if Apache's document root # concurs with nginx's one # #location ~ /\.ht { # deny all; #} listen [::]:443 ssl ipv6only=on; # managed by Certbot listen 443 ssl; # managed by Certbot ssl_certificate /etc/letsencrypt/live/mydomainexample.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/mydomainexample.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot }

Anybody knows how I can solve this on nginx? I want to have my forum displayed at example.com/forums instead of example.com

I've seen it already but my server is already set up and the structure is very different from the one in the thread there. I just keep getting this error when trying to enable rewriting

Do you know where I could get the rewrite rules for nginx maybe? Did some research and found that IPB only supports apache officially

I assume domain.com/index.php would redirect to the forum but what if I want domain.com/forums instead of the index.php?

My default is opening the forum at domain.com or domain.com/index.php not /forums - /forums gives a 404 error How would I access the forum on /forums if I set the server to open index.html as my default page?

The forums, I don't have pages. I'm making a static landing page in html that I want to use it later

How would you go about it if it's already in the root then?

Static HTML