Skip to main content
Topic: SSL and NON SSL fixing and PHP 7.2 (Read 1894 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

SSL and NON SSL fixing and PHP 7.2

Hi All,
I have a few basic question as I am moving from SMF 2.0.15 to Elkarte 1.1.1

1.  I have on my hostera LetsEncrypt SSL where the host foces all call to be rerouted to SSL.
But as I have converted via the importer to Elkarte, it could be, that my old SMF had still links to
normal http links in my forum...
Is there any tool to correct this and change all links from http to https ?

2. Is Elkarte 1.1.1 able to run under PHP 7.2 ?
Does it bring any speed enhancements versus PHP 7.1
User Feline from PortaMX has changed her forum to PHP 7.2 and said the JS and CSS Minifying
and ZIP compressing is really giving much more speed.... So can we do this also already on Elkarte 1.1.1
too ?

Many thanks.
Regards, Stefan.

Re: SSL and NON SSL fixing and PHP 7.2

Reply #1

Quote from: hartiberlin – User Feline from PortaMX has changed her forum to PHP 7.2 and said the JS and CSS Minifying
and ZIP compressing is really giving much more speed.... So can we do this also already on Elkarte 1.1.1
too ?
If your Hoster have enabled the PHP Opcode precompiling, then you can use that.
Call your hosting how to can do this .. it's mostly different on any hosting ..
Also your Hoster must support compressing .. and for this you need a additional .htaccess they handle that.
The code in the .htacces checks if the destination can handle zip compressed transfer.

Normaly this part of .htaccess works on Apache ...
Code: [Select]
# compression
<IfModule mod_deflate.c>
 # Serve gzip compressed CSS files if they exist
 # and the client accepts gzip.
 RewriteCond %{HTTP:Accept-encoding} gzip
 RewriteCond %{REQUEST_FILENAME}\.gz -s
 RewriteRule ^(.*)\.css $1\.css\.gz [QSA]

 # Serve gzip compressed JS files if they exist
 # and the client accepts gzip.
 RewriteCond %{HTTP:Accept-encoding} gzip
 RewriteCond %{REQUEST_FILENAME}\.gz -s
 RewriteRule ^(.*)\.js $1\.js\.gz [QSA]

 # Serve correct content types, and prevent mod_deflate double gzip.
 RewriteRule \.css\.gz$ - [T=text/css,E=no-gzip:1]
 RewriteRule \.js\.gz$ - [T=text/javascript,E=no-gzip:1]

 <FilesMatch (\.js\.gz|\.css\.gz)$>
 # Serve correct encoding type.
 Header append Content-Encoding gzip

 # Force proxies to cache gzipped &
 # non-gzipped css/js files separately.
 Header append Vary Accept-Encoding
 </FilesMatch>
</IfModule>

Fel
Many are stubborn in relation to the path, a few in relation to the target.
Visit our new Forum Project on https://www.portamx.com

Re: SSL and NON SSL fixing and PHP 7.2

Reply #2

Quote from: hartiberlin – Is there any tool to correct this and change all links from http to https ?
Just to be sure I understand well your question, do you want to change all your links inserted in the messages of your forum from "http://myforum.domain"  to" https://myforum.domain"? If so, you can do it in two ways:
  • set up a redirect in htaccess file, just google "redirect http to https htaccess", there are lots of tutorials
  • or you can change them into the database by running a sql command: (do a a backup first, or do it on a test forum)
    Code: [Select]
    UPDATE elkarte_messages set body = REPLACE(body,  'http://mydomain', 'https://mydomain');
I did both on my forum, and I did it also for signatures and PM.
Quote from: hartiberlin –
2. Is Elkarte 1.1.1 able to run under PHP 7.2 ?
my test forum is running on php 7.2 and seems to work fine for now
Quote from: hartiberlin – Does it bring any speed enhancements versus PHP 7.1
I have no idea  :-[
Quote from: hartiberlin – JS and CSS Minifying and ZIP compressing is really giving much more speed.... So can we do this also already on Elkarte 1.1.1
too ?
Yes, you can do it in ACP > Configuration > Features and Options > General > Minify Javascript and CSS files
sorry for my bad english

Re: SSL and NON SSL fixing and PHP 7.2

Reply #3

Quote from: hartiberlin – Does it bring any speed enhancements versus PHP 7.1
https://community.centminmod.com/threads/php-7-2-0rc6-released.13292/
Unless you have a terribly busy website, it's unlikely you'll notice any difference. IMO.
Bugs creator.
Features destroyer.
Template killer.

Re: SSL and NON SSL fixing and PHP 7.2

Reply #4

1. Fixing url can be done using repair_settings.php tool.

2. Yes, there is improvement in using php7.2.

Re: SSL and NON SSL fixing and PHP 7.2

Reply #5

Is Feline from PortaMX still alive ?

PortaMX has also been down now for more than a year at least..
Also the PortaMX was probably sold or not renewed anymore...

So is she still live ??

Regards, Stefan.

Re: SSL and NON SSL fixing and PHP 7.2

Reply #6

Her profile says:

Date Registered: August 14, 2014, 08:38:18 pm
Last Active: July 26, 2021, 05:07:36 pm

hmm..


Re: SSL and NON SSL fixing and PHP 7.2

Reply #8

It appears the domain expired then got bought by someone else.
The new owner seems to be Italian, not German. Feline's language in her profile states German.
So, maybe she decided to drop everything and move onto something else.

Re: SSL and NON SSL fixing and PHP 7.2

Reply #9

Yes, you are right.
It expired and got bought by this new owner:

Owner and Data Controller
Skynet World Trading, 16/355 Liverpool St., Darlinghurst, 2010, Nsw, Australia.
Owner contact email: elia.business@yahoo.com

So it seems the PortaMX Forum is history and will no longer be supported ??

Thanks.
Regards, Stefan.

Re: SSL and NON SSL fixing and PHP 7.2

Reply #10

Really not sure what happened since covid19.
Quote from: hartiberlin – So it seems the PortaMX Forum is history and will no longer be supported ??
Seems like it.

Re: SSL and NON SSL fixing and PHP 7.2

Reply #11

As here are alsoo many users who used SMF previously,
I wanted to know,
how I can remove all MODs from SMF 2.019,
especially  PortaMX Portal Mod.
I tried uploading the SMF 2.019 Upgrade package by extracting all files
and started it from a subdirectory, then it run through until at the end came an error...

also with repaiir-settings.php I could not fix it by deleting all the hooks...
and verifying all the right adress folder links...

and now when I call up my domain there is always an error with the PortaMX Portal being not
valid for the DSGO or something like this...

Could I just fix it if I remove all the PortaMX tables from the database with PHPMYADMIN ?
Is this enough to remove all the PortaMX portal Mod functions from my forum ?

Or do I need also to modify any other PHP files somehow ??

Many thanks.
P.S: I had SMF 2.015 installed and wanted to update it to SMF 2.019
but there were some parser errors listed , but I did the updates anyway...
So now it is broken and as the PortaMX Mod is no longer updated and Felines PortaMX Domain has gone,
I would rather install SimplePortal oder TinyPortal..

Re: SSL and NON SSL fixing and PHP 7.2

Reply #12

Here are the error messages;
Now it says, when I call up my domain:

Call to undefined function pmx_checkECL_Cookie()

And the SMF Upgrade Utility
says:
  • Step 4: Database Changes
  • Step 5: Delete Upgrade
83%
 
Overall Progress

100%
 
Step Progress

Time Elapsed: 0 mins, 11 seconds.
Database Changes
Executing database changes
Please be patient - this may take some time on large forums. The time elapsed increments from the server to show progress is being made!

Database Updates Complete! Click Continue to Proceed.

So it seems it has done all the steps necessary, but  when I continue it says:
at step5:


Fatal error: Uncaught Error: Call to undefined function pmx_checkECL_Cookie() in /www/htdocs/xxxx/yyyyy/Sources/Load.php:425 Stack trace: #0 /www/htdocs/xxxx/yyyyy/smf219/upgrade.php(132): loadUserSettings() #1 {main} thrown in /www/htdocs/xxxx/yyyyy/Sources/Load.php on line 425

So it seems it can not remove the installation files at the end or somethingg like this..
How can I fix this manually ??

Many thanks.
Regards, Stefan.

Re: SSL and NON SSL fixing and PHP 7.2

Reply #13

I do not understand why you asked for SMF help here in ElkArte forum because that is kind of rude. And no, not many of us are still using SMF and most of us have abandoned it, like totally.

So please find your needed assistance from there / them, not us / here, thank you.