Skip to content

Commit 45491cc

Browse files
authored
Merge pull request #527 from ByteInternet/remove-deadlinks-and-references-to-byte-servicepanel
Remove dead links and references to Byte Service Panel
2 parents 209e734 + 444462e commit 45491cc

76 files changed

Lines changed: 211 additions & 390 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/about-hypernode/billing/billing-faq-for-the-control-panel.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ myst:
66
title: Billing Control Panel FAQ | Hypernode
77
redirect_from:
88
- /en/about/billing/billing-faq-for-the-control-panel/
9+
- /en/about/billing/migration-faq/
910
---
1011

1112
<!-- source: https://support.hypernode.com/en/about/billing/billing-faq-for-the-control-panel/ -->

‎docs/about-hypernode/billing/control-panel-billing-facturen-faq-dutch.md‎

Lines changed: 0 additions & 86 deletions
This file was deleted.

‎docs/about-hypernode/security-policies/one-of-your-magento-extensions-is-vulnerable.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,4 +52,4 @@ To verify if your shop is hacked or not, [use the article about recovering a hac
5252

5353
## Need help?
5454

55-
Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to contact [one of these agencies](https://www.magereport.com/page/support).
55+
Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to contact [one of these agencies](https://www.hypernode.com/en/our-partners/).

‎docs/best-practices/email/how-to-export-your-emails.md‎

Lines changed: 2 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,7 @@
22
myst:
33
html_meta:
44
description: Learn how to export your emails from various email clients such as
5-
Byte Webmail, Outlook, Mozilla Thunderbird and Mac Mail. Follow our step-by-step
6-
guide.
5+
Outlook, Mozilla Thunderbird and Mac Mail. Follow our step-by-step guide.
76
title: How to Export your Emails? | Hypernode
87
redirect_from:
98
- /en/best-practices/email/how-to-export-your-emails/
@@ -13,19 +12,7 @@ redirect_from:
1312

1413
# How to Export your Emails
1514

16-
In this article we explain how you can export your email with a number of common email clients and our own webmail application.
17-
18-
## Export email in Byte Webmail
19-
20-
In the Byte webmail client it is not possible to export all the emails at once, so you have to save each email individually.
21-
22-
1. Log in to the Byte webmail application.
23-
24-
1. Click on an email.
25-
26-
1. In the menu item More, select the option 'Opslaan' (.eml)
27-
28-
An .eml file is then created in which the specific email is stored. You can then import this .eml file back into your email client. Please note that you cannot import email into Byte's webmail.
15+
In this article we explain how you can export your email with a number of common email clients.
2916

3017
## Export Email in Outlook
3118

‎docs/best-practices/email/how-to-prevent-spam-being-sent-from-your-name-or-email-address.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ It may happen that others send mail in your name. These could be viruses that ha
2525
The email system does not provide for sender verification, so it is possible to specify anything. However, there a few things you could try to minimise the chances of this happening:
2626

2727
- If you get a lot of responses from a single person, you can have this sender blocked by your mail program.
28-
- If the responses are sent to an address that falls under your Catch All, but that you don't actually use, you can disable this specific address via the Service Panel. For this you create an extra address (the address to which the messages will be sent) and have the mail forwarded to “nobody”. The messages will then be discarded.
28+
- If the responses are sent to an address that falls under your Catch All, but that you don't actually use, you can have this specific address disabled by [support@hypernode.com](mailto:support@hypernode.com). For this you create an extra address (the address to which the messages will be sent) and have the mail forwarded to “nobody”. The messages will then be discarded.
2929
- Tighten your SPF record with -all at the end, so that anything that is not formulated in your SPF record will not be accepted by the receiving mail server.
3030
- Make sure you have SAV enabled in all your mailboxes.
3131
\*\*Please note:\*\*This construction only works if no mailboxes have been selected, and no other external addresses have been specified.

‎docs/best-practices/security/how-hypernode-protects-your-magento-shop.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ redirect_from:
1212

1313
# How Hypernode protects your Magento shop
1414

15-
Due to the standardisation of the ecosystem of Hypernode and our continuous integration pipeline, we can implement changes to all Hypernodes in no time. From the moment a security issue becomes known, a Magento patch for example, [we are able to block security threads on our complete platform in less than 4 hours](https://www.hypernode.com/blog/security/how-hypernode-identifies-and-blocks-new-security-threats-within-the-hour). This way we can offer our customers premium protection.
15+
Due to the standardisation of the ecosystem of Hypernode and our continuous integration pipeline, we can implement changes to all Hypernodes in no time. From the moment a security issue becomes known, a Magento patch for example, [we are able to block security threads on our complete platform in less than 4 hours](../../about-hypernode/security-policies/hypernode-security-statement.md). This way we can offer our customers premium protection.
1616

1717
But, this is not only applicable for acute security issues. As Magento nerds we know that development files also need to be protected and that the Magmi tool can create a huge security hazard for example. Such risks are proactively taken care of at Hypernode.
1818

‎docs/best-practices/security/how-to-apply-magento-patches.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -41,9 +41,9 @@ Log on to the shell server. If you don’t how to log on, contact your hosting p
4141

4242
### Step 3: Download and Upload the Patch
4343

44-
To download the correct patch for your webshop you need to know what version of Magento you’re using. Don’t know what version you use? Find out using [this tutorial](https://www.euperia.com/development/how-to-find-the-magento-version/844).
44+
To download the correct patch for your webshop you need to know what version of Magento you’re using. Don’t know what version you use? You can find it in the back-end of your Magento shop under **System > Tools > Compilation**, or by checking the `app/Mage.php` file.
4545

46-
Download the patch(es) you need via the [Magento downloads page](http://magento.com/security/patches). Upload the patch with SSH to your Magento folder.
46+
Download the patch(es) you need via the [Magento downloads page](https://magento.com/security/patches). Upload the patch with SSH to your Magento folder.
4747

4848
### Step 4: Apply the Patch
4949

@@ -56,11 +56,11 @@ app@abcdef-example-magweb-cmbl:~/magento$ bash patch_supee-5994.sh
5656

5757
### Step 5: Clear Your Cache
5858

59-
It’s important to flush the Magento cache after applying the patch. Flushing your caches can be done in the back-end of your Magento shop under Cache management. More info about flushing your cache in the back-end of Magento can be found in the [Magentocommerce Knowledgebase](http://www.magentocommerce.com/knowledge-base/entry/cache-storage-management/%09200). Don’t forget to flush your OPcode or APC cache as well!
59+
It’s important to flush the Magento cache after applying the patch. Flushing your caches can be done in the back-end of your Magento shop under Cache management. More info about flushing your cache in the back-end of Magento can be found in the [Adobe Commerce documentation](https://experienceleague.adobe.com/en/docs/commerce-admin/systems/tools/cache-management). Don’t forget to flush your OPcode or APC cache as well!
6060

6161
### Step 6: Check Your Shop
6262

63-
Don’t forget to check your shop for vulnerabilities after patching and flushing your caches. Magento’s [Security Patch Page](http://magento.com/security-patch) provides a list of signs to look out for to determine whether your site is comprised or not.
63+
Don’t forget to check your shop for vulnerabilities after patching and flushing your caches. Adobe’s [Security Patch Page](https://magento.com/security/patches) provides a list of signs to look out for to determine whether your site is comprised or not.
6464

6565
### Step 7: Clean up the Patch
6666

@@ -103,12 +103,12 @@ In this example only SUPEE-5344 has been applied. When you uninstalled a patch,
103103

104104
**Magereport keeps saying security patch 6482 isn’t installed**
105105

106-
We found out that there are several reasons why Patch 6788 comes out as uninstalled on [MageReport.com.](https://www.magereport.com/page/support), so we recommend you to check the following:
106+
We found out that there are several reasons why Patch 6788 comes out as uninstalled on [MageReport.com.](https://www.magereport.com/), so we recommend you to check the following:
107107

108-
- When compilation is enabled in the backend of your Magento, SUPEE-6482 doesn’t work properly. Disable compilation (navigate to System > Tools > Compilation page and click on Disable button) to make sure the patch works. After disabling compilation, check your site with [MageReport.com.](https://www.magereport.com/page/support) again. If the check still comes out as not installed, try re-compiling.
108+
- When compilation is enabled in the backend of your Magento, SUPEE-6482 doesn’t work properly. Disable compilation (navigate to System > Tools > Compilation page and click on Disable button) to make sure the patch works. After disabling compilation, check your site with [MageReport.com.](https://www.magereport.com/) again. If the check still comes out as not installed, try re-compiling.
109109
- Check if the patch is installed in the correct directory;
110110
- Reload your opcode cache, webserver, php-fpm process and possible other caches. The old code might be still be active;
111111
- Check your shops’ .htaccess. If you’ve made any adjustements in your .htaccess, it’s possible the patch is only partially installed;
112112
- Using a Magento version older than Magento 1.6.1.0? Update to a more recent version. When patching Magento versions older than Magento 1.6.1.0, certain redirects aren’t added.
113113

114-
We hope one of the causes mentioned above can fix your problem. If not, we recommend you to hire a Magento specialist. Unfortunately we can’t help fixing these problems. We’re a hosting company that specializes in Magento hosting. Magento development however is a completely different specialty. A list of Magento developers per country can be found on [MageReport.com.](https://www.magereport.com/page/support)
114+
We hope one of the causes mentioned above can fix your problem. If not, we recommend you to hire a Magento specialist. Unfortunately we can’t help fixing these problems. We’re a hosting company that specializes in Magento hosting. Magento development however is a completely different specialty. A list of Magento developers per country can be found on [MageReport.com.](https://www.hypernode.com/en/our-partners/)

‎docs/best-practices/security/how-to-fix-malicious-javascript-credit-card-hijack.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -174,4 +174,4 @@ We recommend you ‘clean’ your shop following the steps written in the articl
174174

175175
## Need Help?
176176

177-
Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to [contact one of these agencies](https://www.magereport.com/page/support).
177+
Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to [contact one of these agencies](https://www.hypernode.com/en/our-partners/).

‎docs/best-practices/security/how-to-install-magento-patch-supee-8788-and-release-1-9-3.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ This patch fixes about 17 issues, some of which are highly critical. They allow
1919

2020
## How to Install the Patch
2121

22-
Follow the regular patch instructions. If you run into problems, please visit the [8788 answers page at the StackExchange](http://magento.stackexchange.com/questions/140550/security-patch-supee-8788-possible-problems).
22+
Follow the regular patch instructions. If you run into problems, please visit the [8788 answers page at the StackExchange](https://magento.stackexchange.com/questions/140550/security-patch-supee-8788-possible-problems).
2323

2424
Notably: the patch contains binary characters. So you should probably not open it with a regular editor, as that will mangle the data.
2525

‎docs/best-practices/security/how-to-protect-magento-against-brute-force-attacks.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -165,8 +165,8 @@ Disclaimer: these configuration snippets are provided “as is” and we do not
165165

166166
### Amasty Improved Layered Navigation (Magento 1)
167167

168-
Do you have a Magento 1 shop and do you use the Amasty extension? You may be open to bruteforce attacks if you have a vulnerable version of the Improved Layered Navigation plugin installed. Try visiting the path `/amshopby/adminhtml_filter` (e.g. [www.example.com/amshopby/adminhtml_filter](http://www.example.com/amshopby/adminhtml_filter)) and check if you are redirected to your admin login page. If so, follow the instructions above to restrict access to this path.
168+
Do you have a Magento 1 shop and do you use the Amasty extension? You may be open to bruteforce attacks if you have a vulnerable version of the Improved Layered Navigation plugin installed. Try visiting the path `/amshopby/adminhtml_filter` (e.g. `www.example.com/amshopby/adminhtml_filter`) and check if you are redirected to your admin login page. If so, follow the instructions above to restrict access to this path.
169169

170170
## Need help?
171171

172-
We do not provide Magento consultancy ourselves, however we partnered with professional agencies that will be able to help you. Don’t hesitate to [contact one of these agencies](https://www.magereport.com/page/support).
172+
We do not provide Magento consultancy ourselves, however we partnered with professional agencies that will be able to help you. Don’t hesitate to [contact one of these agencies](https://www.hypernode.com/en/our-partners/).

0 commit comments

Comments
 (0)