Magento 2 Installation Is Incomplete Check the Console Log for Errors Before Trying Again

Contents

• ane Magento Assist
  • i.i "After install I get 'Fatal mistake: Uncaught Error: Phone call to a member role getNext() on cipher in Interceptor.php'"
  • 1.2 "After install I get a '500 Internal Server Error' in the browser"
  • 1.3 "Later install I become a fatal error, with 'Unable to retrieve deployment version of static files from the file organisation' in the reports"
  • 1.4 "When entering the license primal, it spins and doesn't salvage"
  • one.5 "Later install I become images missing, or a server fault: 'Forbidden: PHP is disable.'"
  • 1.6 "I meet an unstyled admin page"
  • 1.seven "I get this error: 'The following modules are outdated'"
  • i.8 "When I activate a plugin, I get a 'circular dependency' error in admin"
  • one.ix "Running compile hangs with no errors"
  • one.10 "I get an error like 'Base table or view not found: (eg. moogentoshipeasycolumn) doesn't be'"
  • ane.11 "I see empty tables in the plugin config folio"
  • 1.12 "I get this error: 'Exception Printing is Disabled by Default for Security Reasons'"
  • i.13 "The Moogento license & config sections become blank & I get this error: '(Zend_Http_Exception): Invalid header line detected : Zend_Http_Response::extractHeaders'"
  • 1.14 "When loading the Orders or Catalog page, I see a 'server fault', or 'Attention: Something went wrong', but just with a specific user"
  • 1.15 "When loading the Orders or Catalog page, after an upgrade, some interactive parts don't work"
• 2 PickPack (M2):
  • two.ane "After install I become a 'Unknown module(south): 'Moogento_PickPack' error"
  • 2.two "The admin user is logged out when trying to print PDFs."
  • 2.3 "Afterward install I see missing images or strange formatting in the PDF editor"
  • 2.4 "I see text links instead of dainty images!"
  • ii.5 "When compiling a plugin, I become: 'Course 'PHPUnit\Framework\TestCase' not plant in ... mPDFTest.php'."
    • two.five.1 tldr;
      • 2.5.1.1 Are yous running Magento < 2.2 ?
    • ii.5.ii Installing PHPunit
  • 2.half dozen "The printed date doesn't friction match the engagement showing in the Orders page"
  • 2.7 "I'yard using Magento 2.2.7 and having email-related errors"
  • two.8 "I get this error: 'Class Zend\Mime\PartFactory does not be in [Moogento\PickPack\Mail service\Template\TransportBuilder\Interceptor]'"
  • ii.ix "I become this error: 'Alarm: file_put_contents(/var/tmp/moogento/pickpack/pdf.html): failed to open stream: No such file or directory'"
  • 2.10 "I get this fault: 'Fatal error: Interface 'Magento\Framework\Filter\SimpleDirective\ProcessorInterface' not found'"
  • 2.11 "I get this error: 'libpng alert: iCCP: known incorrect sRGB profile'"
  • 2.12 "I get this error: 'libpng alarm: Interlace handling should be turned on when using png_read_image'"
• three ShipEasy (M2):
  • 3.1 "When installing, after running compile on production, I become an mistake 'The directory /var/generation cannot be deleted'"
  • 3.2 "Later install I encounter a spinning bike in the Orders page which doesn't go away"
  • three.three "When triggering emails (eg. via Ship & Invoice), we have bug."
  • 3.4 "When editing a shipping address from the orders page (by clicking the pencil icon) I get an error."
  • 3.5 "The Orders folio doesn't work correctly with the Amasty 'Extended Guild Grid' module installed"
• four StockEasy (M2):
  • 4.ane "When installing and running update, I get an error 'Uncaught Fault: Cannot instantiate interface'"
• 5 Selection-n-Scan (M2):
  • 5.ane "I want to always launch the app in fullscreen"
• 6 "I however accept issues"
  • vi.1 Cheque you're using a supported version of PHP & Magento
  • 6.2 Check log files
    • 6.2.i Enabling debug logging
    • half dozen.ii.ii Disabling debug logging
  • 6.3 Check file ownership permissions
  • six.4 Disabling extensions
    • 6.iv.ane Removing extensions
  • 6.5 "How long volition it take to investigate and fix my issue?"
    • vi.five.1 "Why is my issue resolution ETA not Right Now???!!!"
  • six.6 "I found some encrypted portions of code, accept I been hacked?"
    • 6.vi.ane Having issues opening or unzipping with Windows?
• 7 "I stilll accept issues!"
  • 7.1 "How practise I requite you Magento access?"
  • vii.2 "Where do I find the license key?"

Magento Help

Something unexpected happened?

Attempt not to worry too much, take a deep breath and read through these common problems and solutions below.

Nigh bug have been seen earlier and are quickly fixable or at least revertible-from.

"Afterward install I get 'Fatal mistake: Uncaught Error: Phone call to a member part getNext() on null in Interceptor.php'"

Check that you've run setup:di:compile, from the Magento root:

php bin/magento setup:di:compile

If that doesn't work right away, we tin can get a bit deeper:

php bin/magento maintenance:enable

rm -rf generated/ var/view_preprocessed/ var/composer_home/cache/ var/cache/ var/page_cache/

php bin/magento setup:upgrade

php bin/magento setup:di:compile

php bin/magento setup:static-content:deploy -f

php bin/magento cache:flush

php bin/magento maintenance:disable

"After install I get a '500 Internal Server Error' in the browser"

1. Check your server error logs starting time:

   Where this is volition depend on your server. Here's some mutual examples:

   Centos: {server root}/var/log/httpd/

   Debian, Ubuntu: {server root}/var/log/apache2/

   MAMP: {Applications}/MAMP/logs/php_error.log apache_error.log

   MageMojo: /home/log/apache/error.log

   Admission eg. via nano /var/log/httpd/apache_error.log

2. If the error isn't apparent in those logs, y'all might have some one-time static content that needs a tickle:
   1. Move pub/static/.htaccess somewhere out of that folder
   2. Delete /pub/static : rm -R pub/static
   3. Run php bin/magento setup:static-content:deploy
   4. Supersede .htaccess in pub/static

   Or in one line:

   php bin/magento maintenance:enable

   mv pub/static/.htaccess pub/.htaccess

   rm -R pub/static

   php bin/magento setup:static-content:deploy

   mv pub/.htaccess pub/static/.htaccess

   php bin/magento maintenance:disable

3. If that didn't assistance, yous might have some quondam composer files causing issues.
   1. Delete /vendor : rm -R vendor
   2. Run composer update

"After install I get a fatal error, with 'Unable to recall deployment version of static files from the file system' in the reports"

Try running:

php bin/magento setup:static-content:deploy

"When entering the license key, it spins and doesn't save"

• Bank check that y'all have the openssl_public_encrypt PHP office enabled on your server

Some dev servers have this off past default

• Also check the organisation logs in var/logs
• Finally bank check your server log files to run into what's happening

If those don't resolve the issue, go in bear upon and we'll check it out.

"Subsequently install I get images missing, or a server error: 'Forbidden: PHP is disable.'"

1. Open /pub/static/.htaccess
2. Prefix the center lines hither with a # (to annotate them out):

   <IfModule mod_php5.c>

   php_flag engine 0

   </IfModule&dt;

   <IfModule mod_php7.c>

   php_flag engine 0

   </IfModule&dt;

   And so they look similar this:

   <IfModule mod_php5.c>

   #php_flag engine 0

   </IfModule&dt;

   <IfModule mod_php7.c>

   #php_flag engine 0

   </IfModule&dt;

3. Besides check the correct magento file permissions are set

"I see an unstyled admin folio"

Seeing some plainer-than-usual displays?

You might have some older static content that needs re-creating.

Try: php bin/magento setup:static-content:deploy -f

"I go this fault: 'The following modules are outdated'"

Information technology might as well say Moogento_{module} db schema version: defined in codebase - {v1), currently installed - {not v1).

1. Load up your Magento database, eg. in phpMyAdmin
2. Observe the {possible_prefix_}setup_module table
3. Observe the entry relating to the module mentioned, eg. 'Moogento_Pickpack'
4. Delete that entry
5. Run bin/magento setup:upgrade to recreate the right line

"When I activate a plugin, I get a 'circular dependency' error in admin"

If you encounter this, your install hasn't completed correctly.

Try this:

1. Check you lot've registered all your dev & live domains in your Moogento account for the correct central.
2. Backup your site files & database
3. Enable Maintenance Mode.
4. Re-copy all plugin files from the latest version.
5. Bank check there'due south not multiple admin users logged in.
6. Reset the install tag, according to this method.
7. Remove generated files (see here for details):

   rm -rf generated/metadata/* generated/lawmaking/* vendor/* var/cache/* var/generation/* var/view_preprocessed/* var/page_cache/* pub/static/frontend/* pub/static/adminhtml/* -R

8. Update composer (re-generate the /vendor folder):

   composer update

   php bin/magento setup:upgrade

9. Compile (re-generate files):

   php bin/magento setup:di:compile

10. Set file & folder permissions:

    find . -type f -exec chmod 644 {} \;

    find . -type d -exec chmod 755 {} \;

11. Bank check the file ownership. You should have a specific server user (not root) that runs magento.

    eg. if that user is 'magento_user:

    chown -R magento_user:magento_user *

12. Update Magento db:

    php bin/magento setup:db-schema:upgrade

13. Reindex & clear caches:

    php bin/magento indexer:reindex

    php bin/magento cache:clean && php bin/magento cache:affluent && php bin/magento cache:enable

14. Disable maintenance mode:

    php bin/magento maintenance:disable

"Running compile hangs with no errors"

Part of running Magento 2 stores is running compile (including when installing plugins):

bin/magento setup:di:compile -vvv

but, sometimes this hangs with no indication what's up.

There's a couple things we tin can do.

• Try with '-vvv' to evidence more than info

bin/magento setup:di:compile -vvv

• In app/bootstrap.php around line 11, enable ini_set('display_errors', 1);

then re-run compile.

"I go an fault like 'Base of operations table or view not found: (eg. moogentoshipeasycolumn) doesn't exist'"

This mostly means there's a mismatch in tables in the database.

The cause is usually an incomplete install, if y'all skipped updates over a long time period, and sometimes from trying to use an extension without registering the license key.

The solution is to restart the module install in Magento, by removing the entry from the 'setup_module' table in your db.

eg. for M2 stockEasy the line is 'Moogento_Stockeasy'. Just remove that line and re-run the M2 database setup command.

1. Delete the relevant line from setup_module, eg:

   

2. Run the db update command:

   php bin/magento setup:upgrade

Removing db entries for the plugins will remove settings related to that plugin

* If y'all have specific settings saved to the plugin that you want to keep, export the relevant tables/entries offset

* Subsequently re-install yous tin can then import/supersede the relevant entries

Suggestions

These are non required, merely to go along the db trim, it tin can be a good idea.

• If y'all're restarting the install, removing tables related to the aforementioned plugin at the same fourth dimension can be a good mode to get a fresh setup.

* Contempo Moogento plugins will usually name the tables like {moogento}_{plugin}_{specific} eg. moogento_stockeasy_columns

* eg. SQL: SHOW TABLES LIKE "%moo%"

^ Don't delete all entries unless you're re-installing *all* moogento modules!

• Too remove entries from core_config_data

* Recent Moogento plugins volition usually proper name the entries similar {moogento or moo}_{plugin}/{specific} eg. moogento_stockeasy/grid_colors

* eg. SQL: SELECT * FROM `mg_core_config_data` WHERE `path` LIKE '%moo%' ORDER By `path` DESC

^ Don't delete all entries unless yous're re-installing *all* moogento modules!

"I see empty tables in the plugin config page"

If you've been updating the module, something might accept gone sideways - try restarting the install.

Just log in to your database (eg. using phpMyAdmin) and find the setup_module table. Search for the line related to the plugin (eg. LIKE %stockeasy%) and delete it, then run the M2 database upgrade:

php bin/magento setup:upgrade

"I go this error: 'Exception Printing is Disabled past Default for Security Reasons'"

This means that you're set to hide errors; this is recommended for production sites, but for developing a site it's helpful to encounter errors.

In app/bootstrap/alphabetize.php and /index.php prepare this (uncommented) at the top of the file:

ini_set('display_errors', one);

This is a bug in older Magento versions which had issues with http2 responses. Here's the prepare (once y'all're updated to M2.three.3+ yous can remove the fix):

i. In /composer.json, add:

composer.json "autoload": { ... "files": [ ... "lib/Zend/Http/Response.php" ] }

It'll then await something like this:

2. Re-create

vendor/magento/zendframework1/library/Zend/Http/Response.php

to

lib/Zend/Http/Response.php

3. In that file, edit these lines:

[Line 185]

if (! preg_match('#^\d|\d(\.\d)*$#', $version)) {

[line 517]

if ($alphabetize === 0 && preg_match('#^HTTP/\d(?:\.\d+)* [i-five]\d+#', $line)) {

4. Run composer dump-autoload

"When loading the Orders or Catalog folio, I see a 'server mistake', or 'Attention: Something went wrong', merely merely with a specific user"

1. 200px

First try logging in equally a unlike user. This error is ordinarily a result of some corruption in the tabular array that records user-specific grid settings (filters, columns etc.), then changing user can get y'all out of a ready in the brusk term.

For a deeper solution, try clearing the ui_bookmark tabular array.

To do this, you lot need to:

1. Access your database (eg. in cPanel you lot can click 'phpMyAdmin', then the database you're using for Magento 2)
2. Browse that ui_bookmark table; this is where user-specific filters, cavalcade setup, column sorts, are stored
3. You lot'll see user_id as a column - yous can either find the specific user id yous demand to clear, or just articulate the lot
4. To articulate, select all the lines, then click 'Delete'

After this follow the instructions below on clearing your browser cache.

If you still have issues after this then you'll want to dig in and discover the core issue.

"When loading the Orders or Itemize folio, subsequently an upgrade, some interactive parts don't work"

You've likely got some former javascript files cached locally - check that you lot've cleared your browser enshroud.

The easiest way to practise this is:

1. (In Chrome, similar in Edge, Firefox, Safari) right-click in the page > 'Inspect'.
2. Then right-click the url refresh push, and 'Empty Cache & Hard Reload'.

PickPack (M2):

"Subsequently install I become a 'Unknown module(s): 'Moogento_PickPack' fault"

If you've just ran:

php bin/magento module:enable Moogento_PickPack

and go that error bulletin, then there's a few things to check:

1. Accept you uploaded pickPack files to the repo? :)
2. Have you gone through our Install Guide?

"The admin user is logged out when trying to impress PDFs."

This is a Magento event, related to Github magento2: Issue #5309

Other users take suggested editing the .htaccess or conf file to something like this:

php_value session.cookie_lifetime 86400

php_value session.gc_maxlifetime 86400

and then setting the Admin Session timeout to 86400 in the admin config..

"Subsequently install I see missing images or strange formatting in the PDF editor"

Clear static files as above.

"I run across text links instead of overnice images!"

Accept you lot recently cleared /pub/static ?

You're likely missing the /pub/static/.htaccess file. Only copy that back in (from another install if necessary).

"When compiling a plugin, I get: 'Grade 'PHPUnit\Framework\TestCase' non found in ... mPDFTest.php'."

Meet this issue explained & resolved for one case hither.

tldr;

Are you running Magento < 2.2 ?

Yes! Get in touch, yous're a special case :)

No? Read on!

• You demand PHPUnit version at least six.x

• Install that via composer

Installing PHPunit

Try running composer install and/or removing /vendor folder.

If you lot decide to remove that folder then you might use this command, within your Magento root binder:

rm -rf vendor/*

And so go composer to reinstall those modules:

composer update

php bin/magento setup:upgrade

Recompile:

php bin/magento setup:di:compile

If you still have bug, check that your version is correct:

composer show -- phpunit/phpunit

If that's however showing a version less than 6.5, endeavor going into the Moogento_Core and running update:

cd app/code/Moogento/Core

composer update

Besides check, if you're running different PHP versions (eg. on local maybe using MAMP and a fundamental PHP version) that you can admission phpunit:

phpunit --version

^ If this returns an error and so probably the easiest matter to exercise is install phpUnit:

wget https://phar.phpunit.de/phpunit-vi.5.phar

chmod +x phpunit-6.5.phar

sudo mv phpunit-half-dozen.5.phar /usr/local/bin/phpunit

And and so cheque again:

phpunit --version

If you lot're running Magento locally, using something similar MAMP:

one. Copy phpunit into /MAMP/bin/

ii. Edit the bash profile:

nano ~/.bash_profile

then add this after other PATH lines: export PATH=/Applications/MAMP/bin/php/php7.1.12/bin:$PATH

"The printed date doesn't match the date showing in the Orders page"

pickPack allows you to choose which date yous want to impress:

• Printed date
• Ordered appointment
• Invoiced engagement
• Credited appointment
• Shipment date

Only:

1. Edit the folio yous're after
2. Click the 'Free text' cake that you want to add together a date to
3. Place the cursor in the text field for that block, where you lot want to add the date
4. Click the blazon of date you want to add
5. Salvage

• Note you can set the style the date is formatted (eg. '1/ii/19', '1st Feb 2019', etc) in the pickPack Full general config.

"I'thousand using Magento ii.2.7 and having email-related errors"

"I get this error: 'Class Zend\Mime\PartFactory does non exist in [Moogento\PickPack\Mail service\Template\TransportBuilder\Interceptor]'"

If you lot're running a version of Magento less than two.two.eight, there'due south a quick command y'all need to run.

1. Run this command in your master Magento install folder:

   composer require zendframework/zend-mime

2. Follow with the usual Magento update commands.

"I go this mistake: 'Warning: file_put_contents(/var/tmp/moogento/pickpack/pdf.html): failed to open up stream: No such file or directory'"

You've got some permission or ownership issue with your setup (pickPack can't write its temp files while creating the PDFs).

It's time to check Magento 2 file ownership & permissions.

"I become this error: 'Fatal error: Interface 'Magento\Framework\Filter\SimpleDirective\ProcessorInterface' not constitute'"

Please upgrade to Magento 2.3.4+

If you need to run <2.3.iv experience free to become in touch and we can get it working for you.

"I become this error: 'libpng alert: iCCP: known incorrect sRGB profile'"

"I get this error: 'libpng warning: Interlace handling should be turned on when using png_read_image'"

​These are core issues in PHP that are still nowadays in PHP8:

​https://github.com/libgd/libgd/issues/295

​https://bugs.php.cyberspace/issues.php?id=71316

The cause is your catalog having some images saved as png format (we recommend jpeg), and then having those images also saved (eg via Photoshop) with a color contour fastened, or saved as interlaced format.

Y'all're probable to encounter other issues elsewhere with these images so our recommendation is to re-process them:

- ideally as jpegs

- or, re-process them with no color profile and not interlaced pngs

ShipEasy (M2):

"When installing, after running compile on production, I go an fault 'The directory /var/generation cannot be deleted'"

Re-generate static content:

php bin/magento setup:static-content:deploy

If your store isn't in English try this, in this order (eg. here for a French store):

php bin/magento setup:static-content:deploy en_US fr_FR

"After install I run into a spinning cycle in the Orders folio which doesn't become away"

Your install may not have completed correctly.

"When triggering emails (eg. via Send & Invoice), nosotros have problems."

If you're running 2.3.four+, it's stricter when processing templates - cheque that you don't have incomplete IF clauses in templates.

1. Try re-running the installation compile commands.
2. Bank check that your file & folder permissions are correct:
   1. The Magento file system user should have full control (read/write/execute) of all files and directories
   2. That user must not exist the same user as the web server user
   3. The web server user must accept write admission to these files and folders:

      /var app/etc

      /pub

      /generated (since 2.2.one)

   4. The web server user group must own the Magento file organisation so the Magento user (who's in that group) can share file access with the web server user.

      (Including files created by the Magento Admin or other web-based utilities)

   cd {root Magento folder}

   observe . -type f -exec chmod 644 {} \;

   discover . -type d -exec chmod 755 {} \;

   find ./var -blazon d -exec chmod 777 {} \;

   discover ./pub/media -type d -exec chmod 777 {} \;

   find ./pub/static -type d -exec chmod 777 {} \;

   chmod 777 ./app/etc

   chmod 644 ./app/etc/*.xml

   chown -R :{web server grouping} .

   chmod u+10 bin/magento

And then clear the caches:

php bin/magento cache:clean && php bin/magento cache:flush && php bin/magento cache:enable

"When editing a shipping address from the orders page (by clicking the pencil icon) I go an error."

If you've recently updated, please check you lot've still got the custom accost parts selected in the shipEasy config.

"The Orders page doesn't work correctly with the Amasty 'Extended Order Grid' module installed"

Aka Amasty_Ogrid.

Download and install this patch:

https://moogento.com/downloads/ShipeasyAmastyOgridCompatible.zip

The grid should now load correctly.

StockEasy (M2):

"When installing and running update, I get an error 'Uncaught Error: Cannot instantiate interface'"

Effort this: rm -rf var/page_cache var/cache var/composer_home var/generation generated/code generated/metadata var/di var/view_preprocessed/* redis-cli FLUSHALL

If y'all're running redis simply that command doesn't show a consequence, then y'all should cheque with your host the correct command to use.

Pick-northward-Scan (M2):

"I want to ever launch the app in fullscreen"

Pick-n-Scan has an choice in Config to show a 'fullscreen' button, which so shows up in the 'hamburger' menu.

Once clicked, the app volition become fullscreen and you'll accept more vertical space.

If you'd like to launch this fullscreen - this can make sense for warehouse scanning devices - then you just need to 'save to homescreen' the relevant url.

Here'south the steps to add the homescreen shortcut on Chrome (other browsers volition be similar) on Android (iOS is also like):

1. Launch "Chrome" app.

2. Open the URL yous want to pivot to your home screen (ie. navigate to the scan screen from the Orders folio)

3. Tap the carte du jour icon (3 dots in upper right-hand corner) and tap 'Add to homescreen'.

four. You'll be able to enter a proper noun for the shortcut (eg. "Option-n-Scan") and and so Chrome volition add it to your dwelling screen.

5. Now when launching the url via clicking that new icon, it should launch fullscreen (with no accost bar).

"I still have bug"

Bank check y'all're using a supported version of PHP & Magento

1. Bank check which version of PHP your version of Magento supports

   If you're not running a supported version, suspension the install and consider changing your installed PHP version

2. Open {plugin}/composer.json and check the PHP & Magento versions that are supported match what you're running

Check log files

Your Magento 2 debug log file should be located here:

var/log/debug.log

If you haven't turned on logging do so now.

Enabling debug logging

Via Admin backend

Via CLI

php bin/magento config:gear up --enable-debug-logging=true && php bin/magento cache:flush

If you get a --lock mistake then try this:

php bin/magento config:ready --lock --enable-debug-logging=true 1 && php bin/magento cache:affluent

Disabling debug logging

php bin/magento config:prepare --enable-debug-logging=false && php bin/magento cache:flush

1. • Try running Magento and then check those log files - the default location is /var/log
   • Add a number to the log filenames to see recent messages simply.
2. Side by side, check your server log files for errors (location will depend on your server - expect for php and server log files).

Check file ownership permissions

If you didn't go this done when setting up Magento, or installed the plugin nether a server user that's not the one that owns the Magento files, you might demand to check this.

Check Magento 2 File Ownership and Permissions

Disabling extensions

Still problems? Permit's turn it off:

1. Disable the extension :

   php bin/magento module:disable Moogento_PickPack --clear-static-content

2. Disable other Moogento code if you like:

   php bin/magento module:disable Moogento_License --articulate-static-content

   php bin/magento module:disable Moogento_Core --articulate-static-content

   ^ Don't exercise this step if you want to leave other Moogento plugins running!

   *Or*, disable all in i line:

   php bin/magento module:disable Moogento_Core Moogento_License Moogento_Shipeasy

3. Recompile:

   php bin/magento setup:di:compile

   Update the db:

   php bin/magento setup:upgrade

4. Articulate caches:

   php bin/magento cache:make clean && php bin/magento cache:affluent

Removing extensions

Need to remove all files related to our plugins?

Don't forget to drib united states of america a line if something is going incorrect, as we can normally help :)

Via CLI:

1. Disable the plugins first, as per above
2. Navigate to the Moogento parent folder:

   cd /app/lawmaking/Moogento/

3. Cheque what'south there:

   ls

4. Remove the plugin binder:

   rm -rf {extension name: eg. PickPack}

5. Clear cache and indexes and log out/in

Via FTP:

1. Disable the plugins first, equally per above
2. Download the latest version you lot have access to from your business relationship
3. Compare those files and folder construction with what you take installed
4. Remove those files, starting with /app/lawmaking/Moogento/{plugin proper noun}
5. Clear cache and indexes and log out/in

Then in your DB:

1. Find the `setup_module` in your db
2. Detect the entry for the Moogento module(s) you want to remove
3. Delete those entries
4. Find the `core_config_data` in your db
5. Search path for '%LIKE% moogento'
6. Select the relevant entries and delete

   ^ this volition delete your saved config settings for the module(s)

"How long will it take to investigate and fix my upshot?"

If you lot've got in touch with a issue or custom work asking, we'll become back to you with a rough ETA.

We do all work in the order that they come in, with some sorting based on the Maintenance Plan you're on.

We can't brainstorm the piece of work (or the ETA timer) until we take correct access details, so please make sure yous send correct ones.

"Why is my outcome resolution ETA non Correct Now???!!!"

Estimates for development piece of work are necessarily vague, information technology may exist faster or slower than the ETA we send you.

It takes time to properly investigate bug reports, and program feature requests, and we're a small-scale team - nosotros go as fast equally nosotros can but please don't expect magical instant development work :)

Also worth bearing in listen that we reply to support requests ourselves, so if you email every mean solar day for an update and then you'll be directly slowing downward your consequence resolution.

"I found some encrypted portions of lawmaking, have I been hacked?"

All our code is open for you to edit.

Nosotros practise accept a couple of modest blocks of encrypted lawmaking which are part of our licensing system. These need to be left unedited for your extension to work.

If you're worried that you've been hacked and have some unauthorised code, the easiest way to check these specific files is to compare that lawmaking with the aforementioned file from the extension zip, downloaded from your Moogento account. Annotation that this code will sometimes alter between versions, and then make sure you're comparison the aforementioned version.

Having issues opening or unzipping with Windows?

Using "Windows Defender" and it's blocking a download?

1. Click "Internet Options" in the 'All Control Console Items' window
2. Click the "Security" tab
3. Click the "Default Level" push button (Medium-High)
4. Click the "Custom Level…" button
5. Scroll down to "Downloads", then click the "Enable" radio button
6. Click the "OK" button to relieve changes
7. Click "OK" again to close the 'Internet Options' dialog

Is Windows blocking an unzip?

1. Correct-click on the file
2. Select Properties
3. (Make sure you lot are in the Full general tab)
4. Select the Unblock button
5. Click Apply/OK and exit
6. The file will be unblocked

Or try this:

1. Click to the Windows Security Dashboard

   

2. Get to 'Virus & threat protection'

   

3. Click 'Manage settings'

   

4. Disable 'Real-time protection'

   

5. You should now be able to unzip the download.
6. When complete, don't forget to re-enable this setting.

"I stilll have problems!"

• Driblet us a line with:

1. your (South)FTP & SSH admission details
2. Magento admin access
3. which version of Magento
4. which PHP version
5. which Moogento plugin & version

Before getting in touch, please:

• turn on Magento logging,
• turn off Magento compilation,
• provide details of whatever opcode or db cache systems and their logins,
• provide the path to your server log files
• include your order id or license key

"How do I give you lot Magento admission?"

Tried all the suggestions above and need us to take a look? Not sure how to practice that?

1. Log into your Magento site
2. Copy the URL from the browser and add it to your email to usa.
3. Next become to
4. Make a username and countersign and add together that to the electronic mail to us.
5. then click User Role in the left column and assign us the role of Administrator.

Done!

"Where do I find the license central?"

We demand your order id or license key earlier we tin can assist with support. Because, you know. :)

1. Go to
2. Click the 'License' section at the top of the page to aggrandize it.
3. Copy the value from the 'License Key' field.
4. Paste that in your email that to us.

otoolecoureat48.blogspot.com

Source: https://moogento.com/guides/Installing_Magento_2_Extensions_:_Troubleshooting