Quote from Nyheter og oppdateringer

We have just released new versions of our products:

• WoltLab Suite 5.2.7
• WoltLab Suite 3.1.15
• WoltLab Suite 3.0.25

Stability releases (also known as "minor releases") aim to solve existing problems in the current version. Like every stability release, they do not introduce new features; It is strongly recommended to apply these updates.

Applying System Updates

Open your Administration Control Panel and navigate to Configuration > Packages > List Packages. Please click on the button Search for Updates located in the right corner above the package list.

Notable Changes

The list below includes only significant changes, minor fixes or typos are generally left out.

WoltLab Suite Blog

• The link to show more blogs in the user profile was broken. 3.1

WoltLab Suite Calendar

• Inconsistent use of the icon to share an event. 5.2

WoltLab Suite Filebase

• The [file] bbcode is now properly recognized as a block level element. 3.1 5.2

WoltLab Suite Forum

• Incorrect encoding of object names in conditions. 5.0 5.1 5.2
• Restoring the only post of a thread caused incorrect counter updates. 5.1 5.2
• The restrictions on the minimum length and word count of threads was not applied correctly. 5.1 5.2
• External links had not been excluded from the sitemap. 5.1 5.2
• Editing a post and inserting quotes did not yield notifications. 5.1 5.2
• Publishing a thread with an updated time did not update the post dates. 5.2

WoltLab Suite Gallery

• The upload button is now hidden if the user is at most allowed to create links to external video sources. 3.1 5.2

WoltLab Suite Core: Konversationen

• Missing phrase in the dialog to edit the subject. 3.1 5.2
• Redundant encoding of special characters in usernames caused recipients failing to validate. 5.2

WoltLab Suite Core: Importer

• WoltLab Burning Board 4.x
  • Custom user profile fields had been imported using incorrect type identifiers. 3.1 5.2

WoltLab Suite Core: Verwarnungen

• Issuing a warning in the user profile did not work previously. 3.1 5.2

WoltLab Suite Core

• Incorrect encoding of object names in conditions. 3.0 3.1 5.2
• Patched jQuery against CVE-2019-11358. 3.0 3.1 5.2
• Exceptions raised in cronjobs are now being forwarded to the global error log. 3.1 5.2
• The notification for expiring paid subscriptions did not properly reflect the number of remaining days. 3.1 5.2
• Resolved conflicts when embedding multiple instances of the comment system on the same page. 3.1 5.2
• The bulk processing for users failed when the conditions matched over 65k users. 3.1 5.2
• Teaser images in articles could sometimes use the wrong translation for the image caption. 3.1 5.2
• Incorrect detection of the large iPad Pro. 5.2
• Legacy attachment bbcodes were incorrectly evaluated, causing them to be converted into thumbnails. 5.2
• Mentions for user groups containing more than one whitespace had not been recognized. 5.2
• Prevent browsers from auto filling in certain password fields in the admin panel. 5.2
• Improved the error reporting for failed SSL/TLS connections. 5.2
• Recreated the Twitch bbcode to comply with their recent API changes. 5.2

kilde: Update: WoltLab Suite 5.2.7 / 3.1.15 / 3.0.25 - Neuigkeiten und Hinweise - WoltLab®

tunhj1 la til en ny fil:

File

Bursdagskaker i meldingssidefeltet

Bursdagskaker i meldingssidefeltet

tunhj1

June 12, 2020 at 7:32 AM

Quote

Bursdagskaker i meldingssidefeltet

tunhj1 la til en ny fil:

File

Bruker Gruppen

Bruker Gruppen

tunhj1

June 12, 2020 at 7:20 AM

Quote

Bruker Gruppen

tunhj1 la til en ny fil:

File

Besøk Statistikk

Besøk Statistikk

tunhj1

June 8, 2020 at 7:44 PM

Quote

Besøk Statistikk

tunhj1 added a new file:

File

Skjul for Gjester

Skjul for Gjester

tunhj1

June 5, 2020 at 5:15 AM

Quote

Skjul for Gjester

Quote from Nyheter og oppdateringer

We have just released new versions of our products:

• WoltLab Suite 5.2.6
• WoltLab Suite 3.1.14

Stability releases (also known as "minor releases") aim to solve existing problems in the current version. Like every stability release, they do not introduce new features; It is strongly recommended to apply these updates.

Recent Investigations on Compromised Communities

We have become aware that a few customer sites have been compromised in an attempt to steal user credentials. The attacker did modify a few files to capture plaintext passwords and installed a backdoor in order to regain access at a later point. This update will overwrite the files containing the malicious changes with the original versions.

Furthermore, any intercepted plaintext password was stored in the database column logToken in the table wcf1_user that was added by the attacker. This update will nullify those values by replacing them with the string compromised, account that did not have the password stolen will have an empty value.

If you have any questions or to seek advice if your site had been compromised, please get in touch with us, we'll help you.

How Did the Attacker Gain Access?

Investigations strongly indicate that the attacker gained access to the systems by logging in with an administrator's account using credentials that have been stolen previously. We cannot stress this enough: DO NOT REUSE PASSWORDS ON OTHER SITES. YOU PUT YOURSELF AND YOUR COMMUNITY AT RISK!

Performing System Updates

Open your Administration Control Panel and navigate to Configuration > Packages > List Packages. Please click on the button Search for Updates located in the right corner above the package list.

Notable Changes

The list below includes only significant changes, minor fixes or typos are generally left out.

(Will be added later.)

Display More

kilde: Update: WoltLab Suite 5.2.6 / 3.1.14 - Neuigkeiten und Hinweise - WoltLab®

Quote from Nyheter og oppdateringer

WoltLab Suite 3.0 was released on January 11th 2017 and its guaranteed support period has ended on Feburar 28th, 2020, two years after the final release of its successor WoltLab Suite 3.1. We'll continue to provide security updates for the WoltLab Suite 3.0 series for a limited time, before dropping the support entirely.

Affected Products

• WoltLab Suite Forum 5.0
• WoltLab Suite Core 3.0
• WoltLab Suite Blog 3.0
• WoltLab Suite Calendar 3.0
• WoltLab Suite Filebase 3.0
• WoltLab Suite Gallery 3.0

March 1st, 2020 - Stage 1

• End of the regular support period.
• Updates will be released for security issues only.
• PHP 7.4 is the last supported PHP version.

March 1st, 2021 - Stage 2

• End of the extended support period, there will be no more updates being released.
• The ticket support will be limited to the WoltLab Suite 3.1 and newer products only.

March 1st, 2022 - Stage 3

• The downloads in the customer area will be removed.
• The package update servers for the affected products will be shut down.
• Any files in the Plugin-Store for these versions will be removed.

kilde: Limited Support for WoltLab Suite 3.0 - Neuigkeiten und Hinweise - WoltLab®

Quote from Nyheter og oppdateringer

We have just released new versions of our products:

• WoltLab Suite 5.2.5
• WoltLab Suite 3.1.13
• WoltLab Suite 3.0.24

Stability releases (also known as "minor releases") aim to solve existing problems in the current version. Like every stability release, they do not introduce new features; It is strongly recommended to apply these updates.

Users Sending Emails to Users

The software contains a legacy feature that enables users (and if configured, also guests) to send emails to other users. This feature has little use today, but is more often than not overlooked by administrators, especially those migrating from previous versions. The form uses a dedicated group permissions that was enabled by default in previous versions and was often left unchanged.

It has come to our attention that attackers take advantage of this feature and actively abused it to send out spam emails to other users. We've taken two steps to mitigate this issue to some extent:

1. Force revoked the group permissions to use this form. Site owner can grant the permissions again at their own discrection, although we strongly advise against this.
2. The captcha protection of the mail form was previously enabled for guest access only and is now enforced for users alike. This is the first form to enforce the captcha for logged-in users too.

This change has previously been applied to the 5.2 series and is now in full effect for the entire WoltLab Suite 3.x series.

Performing System Updates

Open your Administration Control Panel and navigate to Configuration > Packages > List Packages. Please click on the button Search for Updates located in the right corner above the package list.

Notable Changes

The list below includes only significant changes, minor fixes or typos are generally left out.

WoltLab Suite Blog

• Pages excluded from access by search engines were incorrectly listed in the sitemap. 3.1

WoltLab Suite Calendar

• Pages excluded from access by search engines were incorrectly listed in the sitemap. 3.1

WoltLab Suite Filebase

• Pages excluded from access by search engines were incorrectly listed in the sitemap. 3.1
• File owners were unable to delete responses to reviews despire having the permissions. 5.2

WoltLab Suite Gallery

• The list of deleted images raised an exception when viewed by guests. 3.0 3.1
• Pages excluded from access by search engines were incorrectly listed in the sitemap. 3.1

WoltLab Suite Forum

• Attempting to move a thread raised an exception in PHP 7.4. 5.0 5.1
• Pages excluded from access by search engines were incorrectly listed in the sitemap. 5.1 5.2

WoltLab Suite Core: Conversations

• Resolved an issue when replying to conversations when one or more participants were deleted. 3.0 3.1
• The import from vBulletin could fail due to an incorrect recognition of numeric values. 3.0 3.1 5.2

WoltLab Suite Core

• Resolved two compatibility issues with PHP 7.4. 3.0 3.1
• Reading articles yielded an incorrect location in the users online list. 3.0 3.1 5.2
• Requests dispatched through HTTPRequest would not apply the timeout value to the stream itself. 3.0 3.1 5.2
• Improved the behavior of the mobile message UI. 3.1
• Optimized the processing speed of messages with excessive amounts of HTML nodes. 3.1 5.2
• An incorrect sort direction caused packages installed via the package server to sometimes favor older versions over newer ones. 3.1 5.2
• Removed the compatibility check for the API versions. 3.1
• Overly restrictive permission checks for non owner groups. 5.2

Display More

kilde: Update: WoltLab Suite 5.2.5 / 3.1.13 / 3.0.24 - Neuigkeiten und Hinweise - WoltLab®

Quote from Nyheter og oppdateringer

The WoltLab Cloud – Available Now!

The “WoltLab Cloud”, our comprehensive and highly optimized managed hosting solution for the WoltLab Suite, is available now. With WoltLab Cloud, we take care of all technical aspects of the operation, including but not limited to regular maintenance tasks and updates of the software, as well as taking care of daily backups of your site. All WoltLab Suite Apps are already included, the preconfigured Elasticsearch integration offers an enterprise grade search experience for your users.

➡️ Details & Pricing of the WoltLab Cloud

The Strengths of the WoltLab Cloud

We’ve put great emphasis on building a robust and reliable platform that is capable of a stable operation of your site. Optimizing the software and hardware components allow us to deliver an outstanding site experience, with fast response times even on high load.

An overview of the most important perks of the WoltLab Cloud:

• All WoltLab Suite Apps are included.
  • Powered by Elasticsearch for fast and precise search results.
• Full technical support of the installation.
  • Providing a turnkey installation and applying regular software updates.
  • Daily backups of your site are fully encrypted and stored on a different server.
  • Robust DDoS protection on the network layer provided by our partner Voxility.
• Install plugins and styles from the official WoltLab Plugin-Store.
• Optimized and powerful server infrastructure.
  • 100% of your data is stored on enterprise grade SSDs.
  • Custom built servers from Hewlett Packard Enterprise utilizing 2nd generation scalable Intel Xeon Gold processors.
  • Audited tier 3+ data center located in Frankfurt am Main (Germany).
• Full SSL/TLS encryption with certificates issued by Let’s Encrypt.
• Bring your own domain without additional costs.
• The technical operation is fully compliant with the GDPR of the European Union.
  • All data is stored within Germany at all times.
  • Data is transferred over SSL/TLS encrypted connections only.
  • Data Processing Agreement (DPA).
  • Technical and organizational measures in compliance with article 32 of the EU GDPR.

Please refer to the preview Managed Hosting – Introducing the WoltLab Cloud for more information on the WoltLab Cloud.

kilde: Managed Hosting Launched – WoltLab Cloud - Neuigkeiten und Hinweise - WoltLab®

Quote from Nyheter og oppdateringer

We have just released new versions of our products:

• WoltLab Suite 5.2.4

Stability releases (also known as "minor releases") aim to solve existing problems in the current version. Like every stability release, they do not introduce new features; It is strongly recommended to apply these updates.

Users Sending Emails to Users

The software contains a legacy feature that enables users (and if configured, also guests) to send emails to other users. This feature has little use today, but is more often than not overlooked by administrators, especially those migrating from previous versions. The form uses a dedicated group permissions that was enabled by default in previous versions and was often left unchanged.

It has come to our attention that attackers take advantage of this feature and actively abused it to send out spam emails to other users. We've taken two steps to mitigate this issue to some extent:

1. Force revoked the group permissions to use this form. Site owner can grant the permissions again at their own discrection, although we strongly advise against this.
2. The captcha protection of the mail form was previously enabled for guest access only and is now enforced for users alike. This is the first form to enforce the captcha for logged-in users too.

For Developers: Changes to the HTML Markup For .contentItemLink

The new .contentItemList was introduced as a generic implementation for content pieces that rely on teaser images. However, the DOM is somewhat flawed by expecting a link to wrap around the whole content section, which easily collides with certain content elments.

HTML

Code

<a href="…" class="contentItemLink">

<!-- content -->

</a>

Should be changed into:

HTML

Code

<div class="contentItemLink">

<!-- content -->

<a href="…" class="contentItemLinkShadow"></a>

</div>

The CSS remains unaffected, causing no visual change if the old DOM is continued to be used, preserving compatibility with existing implementations. The changes to the CSS is fully backwards compatible, however, we strongly encourage developers to adopt these changes as soon as possible.

Deprecate the use of `<a>` for `.contentItemLink` · Issue #3189 · WoltLab/WCF · GitHub

Performing System Updates

Open your Administration Control Panel and navigate to Configuration > Packages > List Packages. Please click on the button Search for Updates located in the right corner above the package list.

Notable Changes

The list below includes only significant changes, minor fixes or typos are generally left out.

WoltLab Suite Blog

• The generated HTML for the article preview was invalid, causing some parts of the preview to not respond to clicks. 5.2
• Pages excluded from access by search engines were incorrectly listed in the sitemap. 5.2
• The list of articles by tag did not support multiple result pages. 5.2
• New template event in the header section of articles. 5.2

WoltLab Suite Calendar

• Pages excluded from access by search engines were incorrectly listed in the sitemap. 5.2
• The list of events by tag did not support multiple result pages. 5.2

WoltLab Suite Filebase

• Custom input fields of type boolean could not be enabled due to a collision of the HTML id. 5.2
• Pages excluded from access by search engines were incorrectly listed in the sitemap. 5.2
• The list of files by tag did not support multiple result pages. 5.2

WoltLab Suite Gallery

• The list of deleted images raised an exception when viewed by guests. 5.2
• Pages excluded from access by search engines were incorrectly listed in the sitemap. 5.2
• The list of albums and images by tag did not support multiple result pages. 5.2

WoltLab Suite Forum

• Attempting to move a thread raised an exception in PHP 7.4. 5.2
• Incorrect handling of empty threads in the AMP view. 5.2
• The list of threads by tag did not support multiple result pages. 5.2

WoltLab Suite Core: Conversations

• Resolved an issue when replying to conversations when one or more participants were deleted. 5.2

WoltLab Suite Core: Importers

• XenForo 2.x
  • Support for pixel based font sizes and the support for the rgb() format for colors. 5.2
  • Support for additional meta data used with embedded attachments. 5.2
• WoltLab Suite 3.x, 5.x
  • Incorrect recognition of categories for imported media. 5.2

WoltLab Suite Core

• Resolved two compatibility issues with PHP 7.4. 5.2
• New template events in the message sidebar in the rank section. 5.2
• The form to add new phrases sometimes failed the validation of the selected category. 5.2
• Incorrect prompt for i18n articles when attempting to create an article on the category list. 5.2
• Collision of the mobile UI for messages on screen widths between 768 and 1024 px. 5.2
• Improved main menu on oversized tablets that exceed 1024 px screen width. 5.2
• Improved the display of code boxes in the AMP view. 5.2
• The generated HTML for the article preview was invalid, causing some parts of the preview to not respond to clicks. 5.2

Display More

kilde: Update: WoltLab Suite 5.2.4 - Neuigkeiten und Hinweise - WoltLab®

tunhj1 la til en ny versjon:

File

WoltLab Suite Forum 5.2 (Norsk XML Fil)

WoltLab Suite Forum 5.2 (Norsk XML Fil)

tunhj1

March 20, 2020 at 7:22 AM

Quote

Oppdatering

tunhj1 la til en ny fil:

File

Gamification: Userr level

Gamification: Userr level

tunhj1

March 16, 2020 at 5:59 AM

Quote

Gamification: Userr level

tunhj1 la til en ny fil:

File

Gamification Box (user progress)

Gamification Box (user progress)

tunhj1

March 16, 2020 at 5:54 AM

Quote

Gamification Box (user progress)

Quote from Nyheter og oppdateringer

Third Party Package Servers Provided by (Optional) Packages

In recent years, we have seen an increasing number of incidents involving third-party package servers, focusing on packages offered in the Plugin-Store.

In the interest of our customers, we have decided not to approve any new packages or updates that directly or indirectly (e.g. via optional packages) install third-party package servers. This explicitly only affects packages in the plugin store, there is no technical change in the core, it is still possible to create package servers via third-party packages or by manually adding them.

In this context, and in the interests of transparency, we would like to explain the primary reasons for our decision in the following.

Lack of Necessity for Products in the Plugin-Store

For extensions and styles from the plugin store, there is absolutely no need to install third-party package servers, because all updates are delivered directly from the Plugin-Store as soon as they are reviewed.

Distribution of Non-audited Updates

Some third-party vendors release updates for packages directly as soon as they are available and do not wait for the review in the plugin store. This is problematic because the final review of each new package and each update is done manually by a WoltLab GmbH employee.

On average, every third update is rejected at the first attempt due to substantial defects. Early delivery via third-party package servers undermines this review, which aims to reduce both security and stability issues.

Collision with Commercially Offered Products

A special case is the premature release of updates, where the product is offered both in the Plugin-Store and directly by the third-party vendor. This can lead to conflicts if no access data has been stored for the third-party vendor's package server and updates are therefore offered before they are published in the Plugin-Store.

Security Concerns Regarding Unaudited Packages and Updates

The strength of the package system is also one of the biggest weak spots, because extensions can make almost arbitrary changes, up to the execution of security-critical malicious code. This is made more difficult by the fact that package servers can offer updates for almost any package for download, the only exception being our products, which can only be delivered via the official package servers.

Unfortunately, incidents have occurred in which websites of third-party vendors have become the target of attacks, with both takeovers at the DNS level, i.e. the domains pointing to a foreign server, and the direct compromise of the server systems. This also means that an attacker gains control over the packet servers of these providers and can exploit them to deliver malicious code almost without being noticed. A look beyond the horizon reveals that this is by no means a fictitious scenario, but rather a recurring threat, for example with NPM or various Linux distributions, which could often only be prevented by a high level of protection.

Compatibility with the WoltLab Cloud

We will soon start to review extensions and styles in the Plugin-Store for compatibility with the WoltLab Cloud. Entries that pass this test will be marked by us; we do not plan to use some kind of "negative marking" at this time.

The criteria for determining compatibility are as follows:

1. Compatibility with WoltLab Suite 5.2.
2. Outgoing HTTP(S) connections consistently rely on the HTTPRequest class or handle the proxy configuration correctly.
3. No outgoing connections to other TCP or UDP ports.
4. No mass sending of emails.
5. No overlapping with privileges that are subject to restrictions in the context of a managed service, such as direct database administration.
6. Packages that install third-party packet servers are generally excluded.

These criteria are already met by the vast majority of packages, so no significant restrictions are to be expected.

Display More

kilde: Plugin-Store Guidelines and Compatibility with WoltLab Cloud - Neuigkeiten und Hinweise - WoltLab®

tunhj1 la til en ny versjon:

File

WoltLab Suite Forum 5.2 (Norsk XML Fil)

WoltLab Suite Forum 5.2 (Norsk XML Fil)

tunhj1

March 20, 2020 at 7:22 AM

Quote

Oppdatering

tunhj1 added a new file:

File

EasyMedia

EasyMedia

tunhj1

August 7, 2022 at 10:34 AM

Quote

Quote from Nyheter og oppdateringer

We have just released new versions of our products:

• WoltLab Suite 5.2.3
• WoltLab Suite 3.1.12
• WoltLab Suite 3.0.23

Stability releases (also known as "minor releases") aim to solve existing problems in the current version. Like every stability release, they do not introduce new features; It is strongly recommended to apply these updates.

Performing System Updates

Open your Administration Control Panel and navigate to Configuration > Packages > List Packages. Please click on the button Search for Updates located in the right corner above the package list.

Compatibility with PHP 7.4

This update introduces compatibility with PHP 7.4 for the WoltLab Suite 3.0.x and 3.1.x series.

Notable Changes

The list below includes only significant changes, minor fixes or typos are generally left out. Some changes have been applied in 3.1 or 5.2 in earlier updates and are not listed separately.

WoltLab Suite Blog

• Compatibility with PHP 7.4. 3.1 3.0
• Improper encoding of values yielded incorrect data for enriched search results. 3.1

WoltLab Suite Calendar

• Imported events use the custom location name if the imported event from iCal does not expose coordinates. 5.2
• The end data was sometimes uneditable. 3.1 3.0
• Greatly increased the range for the maximum number of repeated event dates. 3.0
• Skip invalid dates in imported iCal exports. 3.0

WoltLab Suite Filebase

• Custom boolean options did not show their value if the user selected "no". 5.2

WoltLab Suite Gallery

• The generated HTML of the album and image bbcode was sometimes invalid. 5.2
• Watermarks have been incorrectly applied to thumbnails of video links. 3.1
• The page location was incorrect for nested categories. 3.1 3.0
• An incorrect number of images were reported inside the album bbcode. 3.1 3.0

WoltLab Suite Forum

• Empty RSS feeds could raise an exception. 5.2
• Moved the reaction button on mobile devices back into the message menu due to several incompatibilities. 5.2
• Threads could be hidden from the thread list if the thread starter is a guest and the current user blocks other users. 5.2
• Custom boolean options did not show their value if the user selected "no". 5.2
• The list of unresolved threads yielded inaccurate results for guests. 3.1
• Incorrect logging of threads that are moved to the trash bin. 3.0
• External links could break the user group permission form. 3.0

WoltLab Suite Core: Conversations

• Incorrect update of usernames when merging a user with another. 3.0
• Leaving a draft conversation yielded an error. 5.2 3.1 3.0

WoltLab Suite Core: Importers

• SMF 2.x
  • Added support for legacy attachment filenames. 3.0
• MyBB 1.x
  • Incorrect recognition of quotation marks inside font bbcodes. 3.1 3.0
• vBulletin 5.x
  • Broader support for different [attach] types. 3.1
  • BBCodes in signatures had not been converted. 3.1
  • Improved the support for pixel based font sizes. 3.1

WoltLab Suite Core

• Improved the compatibility with code that relies on legacy message handling. 5.2
• The system check now validates the availibility of graphics processing libraries. 5.2
• Improved the styling of messages for Google AMP. 5.2
• Backspacing the empty editor in iOS Safari yielded unexpected HTML. 5.2
• The number of pending notification and the favicon where sometimes not updated when the browser tab is running in the background. 5.2
• Mentioning a user group would yield only a single notification. 5.2
• Improved the reaction UI for large touch devices (iPad Pro 12.9"). 5.2
• Chromium based browsers did not properly outdent nested lists in the editor. 5.2
• The upgrade from 3.1 to 5.2 failed in MySQL >= 8.0.19. 5.2
• Adding or editing users could silently fail due to validation errors in the signature text. 3.1
• Converting text lines into code in the WYSIWYG editor using Firefox could cause extra blank lines. 3.1
• User mentiones had a trailing whitespace that caused a small gap between mentiones and the adjacent text. 3.1
• Compatibility with PHP 7.4. 3.1 3.0
• The Facebook login no longer requests legacy scopes that could cause issues. 3.0
• Upgraded the GitHub login due to changes to their API endpoints. 5.2 3.1 3.0
• Resizing the browser window would not always rebuild the dimensions of a dialog. 3.0
• Rebuilding users could causes issues with signatures from newly registered users. 3.0
• Reject access tokens of banned users. 3.1 3.0
• HTML entities were encoded twice in the anchor links of the user profile tabs. 3.1 3.0
• Error logs would sometimes be removed after a delay due to an incorrect time comparison. 5.2 3.1 3.0

kilde: Update: WoltLab Suite 5.2.3 / 3.1.12 / 3.0.23 - Neuigkeiten und Hinweise - WoltLab®

tunhj1 la til en ny versjon:

File

WoltLab Suite Forum 5.2 (Norsk XML Fil)

WoltLab Suite Forum 5.2 (Norsk XML Fil)

tunhj1

March 20, 2020 at 7:22 AM

Quote

Oppdatering

tunhj1 la til en ny versjon:

File

WoltLab Suite Forum 5.2 (Norsk XML Fil)

WoltLab Suite Forum 5.2 (Norsk XML Fil)

tunhj1

March 20, 2020 at 7:22 AM

Quote

Oppdatering

tunhj1 la til en ny versjon:

File

WoltLab Suite Forum 5.2 (Norsk XML Fil)

WoltLab Suite Forum 5.2 (Norsk XML Fil)

tunhj1

March 20, 2020 at 7:22 AM

Quote

Oppdatering...både WoltLab Core og Forum er med i versjon 1.0.4