News:
Bored? Looking to kill some time? Want to chat with other SMF users? Join us in IRC chat or Discord
Recent posts
#21
Modifications and Packages / Re: Simple Audio Video Embedde...
Last post by spiros - Yesterday at 04:31:43 AMI checked in SMF error log and php logs but could not find any further info, it points to zip file.
Code Select
https://www.translatum.gr/forum/index.php?action=admin;area=packages;sa=install;package=SimpleAudioVideoEmbedder7.0.5.zip
fclose(): Argument #1 ($stream) must be of type resource, bool given
#22
SMF 2.1.x Support / Re: my forum was hacked and h...
Last post by Aleksi "Lex" Kilpinen - Yesterday at 04:21:51 AM #23
SMF 2.1.x Support / Re: my forum was hacked and h...
Last post by planetcare - Yesterday at 04:05:19 AMsadly things have gone from bad to worse on my forum as the host seems to have no idea of what to do!
The latest from my host
We have taken several steps to address suspicious files on your website, as previously discussed in tickets #783759 and #770439. However, when implementing the 'script.js' file from the original installer, an error was found displaying 'smc_PopupMenu not defined', which caused the dropdown menu on the username to not work as depicted in the attached screenshot 'inspect-element.png'.
Upon further investigation, it was found that the dropdown menu worked fine when using the presumed 'script.js' file. This suggests that the 'smc_PopupMenu' function may be contained within a suspicious file.
Additionally, unusual lines of code were identified within the suspicious 'script.js' file, as depicted in the attached screenshot 'suspect-script.png'. Due to the complexity of the code and our limited understanding, further investigation was challenging.
As a temporary measure to mitigate the website injection issue, we have chosen to continue using the 'script.js' file from the original SMF 2.0.19 installer.
The latest from my host
We have taken several steps to address suspicious files on your website, as previously discussed in tickets #783759 and #770439. However, when implementing the 'script.js' file from the original installer, an error was found displaying 'smc_PopupMenu not defined', which caused the dropdown menu on the username to not work as depicted in the attached screenshot 'inspect-element.png'.
Upon further investigation, it was found that the dropdown menu worked fine when using the presumed 'script.js' file. This suggests that the 'smc_PopupMenu' function may be contained within a suspicious file.
Additionally, unusual lines of code were identified within the suspicious 'script.js' file, as depicted in the attached screenshot 'suspect-script.png'. Due to the complexity of the code and our limited understanding, further investigation was challenging.
As a temporary measure to mitigate the website injection issue, we have chosen to continue using the 'script.js' file from the original SMF 2.0.19 installer.
#24
SMF 2.1.x Support / Re: @name results in 403
Last post by CRM 114 - Yesterday at 02:43:14 AMQuote from: ColinJM on April 14, 2024, 11:27:52 PM...can this be directed to the login screen and then onto the post please?
Actually this is the normal behaviour, at least at my forum.
#25
SMF 2.1.x Support / Re: How can I empty All keywor...
Last post by @rjen - Yesterday at 02:27:20 AMSo I just checked my test forum, and Indeed, it is Optimus: you conveniently left out the bottom part on your screenshot..
You cannot view this attachment.
I do not know if it is possible to clean out key-words, you need to ask the Mod author in the Suppoprt topic.
What I would recommend is two things:
1. Deactivate the key-words in the settings to stop the list growing more and more
You cannot view this attachment.
2. Check the permissions for membergroups: take it away form users that are polluting it..
You cannot view this attachment.
1. Check the premissions for the user groups:
You cannot view this attachment.
I do not know if it is possible to clean out key-words, you need to ask the Mod author in the Suppoprt topic.
What I would recommend is two things:
1. Deactivate the key-words in the settings to stop the list growing more and more
You cannot view this attachment.
2. Check the permissions for membergroups: take it away form users that are polluting it..
You cannot view this attachment.
1. Check the premissions for the user groups:
#26
SMF 2.1.x Support / Re: How can I empty All keywor...
Last post by @rjen - Yesterday at 01:24:14 AMGo to admin and check the Search Engine Optimization settings (those are the Optimus settings) and uncheck the options on keywords.
I am not familiar with the key words function in Optimus, that's why you should really ask in the mod support thread....
How did you even get to that page in the screenshot?
I am not familiar with the key words function in Optimus, that's why you should really ask in the mod support thread....
How did you even get to that page in the screenshot?
#27
Modifications and Packages / Re: Attachment Browser
Last post by shawnb61 - Yesterday at 01:21:20 AMSome notes when using the Attachment Browser:
- All the column headings are clickable, and when you click on them, it will sort by that column. Clicking a 2nd time will sort in descending order. Handy for seeing items uploaded recently, or items frequently downloaded, etc.
- Many of the fields within the list & grid are clickable - e.g., clicking on the filename will download the file. Clicking on the message subject (list view) or the post date (grid view) will bring you directly to the post that has the attachment.
- Clicking on the "Filter By" button allows you to filter by poster, date range, file extension, and various tags.
- When viewing a filtered list, clicking on the "Search Again" button at the bottom of the list will bring you back to the "Filter By" screen to allow you to tweak the filter.
- All the column headings are clickable, and when you click on them, it will sort by that column. Clicking a 2nd time will sort in descending order. Handy for seeing items uploaded recently, or items frequently downloaded, etc.
- Many of the fields within the list & grid are clickable - e.g., clicking on the filename will download the file. Clicking on the message subject (list view) or the post date (grid view) will bring you directly to the post that has the attachment.
- Clicking on the "Filter By" button allows you to filter by poster, date range, file extension, and various tags.
- When viewing a filtered list, clicking on the "Search Again" button at the bottom of the list will bring you back to the "Filter By" screen to allow you to tweak the filter.
#28
SMF 2.1.x Support / @name results in 403
Last post by ColinJM - April 14, 2024, 11:27:52 PMHI All,
Receiving a 403 if people are logged out and click on the link the @name produces - can this be directed to the login screen and then onto the post please?
Receiving a 403 if people are logged out and click on the link the @name produces - can this be directed to the login screen and then onto the post please?
#29
SMF 2.1.x Support / Re: Images imbedded vs Attache...
Last post by ColinJM - April 14, 2024, 11:26:09 PMThanks Steve.
#30
SMF 2.1.x Support / Re: PHPSESSID in link path css...
Last post by shawnb61 - April 14, 2024, 10:06:08 PMPHPSESSID is put there by php itself, not by SMF.
The session must be kept somewhere. SMF uses cookies.
But... For those brief moments before the cookie exists, php will use PHPSESSID. E.g., first visit, first interaction, no cookie yet.
Normally it's so short-lived, nobody even sees PHPSESSID in the url.
However... If you disable cookies via going incognito, you are forcing your system to do so.
This behavior will be seen on any site that uses php.
But as noted earlier, this is not the cause of your css/js issue... (Or everybody would see the problem...) When we see this, it is normally due to the reasons stated above - url discrepancies.
If only some people are seeing this issue, which appears to be the case, it's possible their browser has cached a funky url. A redirect should address that.
The session must be kept somewhere. SMF uses cookies.
But... For those brief moments before the cookie exists, php will use PHPSESSID. E.g., first visit, first interaction, no cookie yet.
Normally it's so short-lived, nobody even sees PHPSESSID in the url.
However... If you disable cookies via going incognito, you are forcing your system to do so.
This behavior will be seen on any site that uses php.
But as noted earlier, this is not the cause of your css/js issue... (Or everybody would see the problem...) When we see this, it is normally due to the reasons stated above - url discrepancies.
If only some people are seeing this issue, which appears to be the case, it's possible their browser has cached a funky url. A redirect should address that.