I have a clean install of Magento 2 and am trying to create a really simple custom module, but it doesn't seem to recognize any of the code in the module. The module itself shows up in the list in the back-end, and can be enabled, but (for example) custom routes in routes.xml always go to a 404 page.
This is not just happening for new custom modules that I create, but also for modules downloaded from elsewhere. I get a 404 when I install Alan Storm's "Hello World" module (http://alanstorm.com/magento_2_mvvm_mvc) and try to navigate to /hello_mvc/hello/world. I also get a 404 on navigating to /newpage after installing the sample module Sample New Page.
I have cleared the cache, set the mode to developer, run setup:upgrade and setup:di:compile. Other pages, such as the /customer/account/ page, work fine, so it's not the rewriting that's the issue (I don't think).
I'm on Windows 8.1 running WAMP with (the standard) Apache 2.4.18, PHP 7.0.4 & MySQL 5.7.11. I've tried the latest 2 versions of Magento 2 (2.0.4 & 2.0.5) and have the same result.
Unfortunately I didn't get to the bottom of why this was happening, but after a clean install of Magento I have now been able to get this working.
Related
I have started facing an issue with locally hosted Drupal 9 (Xampp, Windows 10). The issue started when I was trying to create events in drupal 9 and I was redirected to Install.PHP page. However, upon checking I was redirected to Update.php and the error seems to be as mentioned below.
Install.PHP page message:
Drupal 9.2.2 Drupal already installed To start over, you must empty
your existing database and copy default.settings.php over
settings.php. To upgrade an existing installation, proceed to the
update script. View your existing site.
Update.php Page Message:
MISSING UPDATES FOR: MEDIA The installed version of the Media module
is too old to update. Update to a version prior to 9.0.0 first
(missing updates: media_post_update_collection_route,
media_post_update_storage_handler,
media_post_update_enable_standalone_url,
media_post_update_add_status_extra_filter).
I'm well aware of the fact that Media is a core module and I havent tried upgrading it or my site. My site has always been a D9 installation and there were no migrations etc. I would really appreciate expert help on this issue.
Running this in a function in my .theme file did the trick for me:
\Drupal::service('update.post_update_registry')
->registerInvokedUpdates(['media_post_update_collection_route', 'media_post_update_storage_handler', 'media_post_update_enable_standalone_url', 'media_post_update_add_status_extra_filter', 'setting functions as applied according_to_the_error_message']);
I personally used hook_theme() (Make sure to clear your cache for it to run and also remove this code once the issue is fixed.)
I installed Magento 2.3 (with demo content) successfully using Installatron in cPanel. But the buttons in Admin menu don't work (not clickable). Beside this, there is a problem on the front end: product images don't load on the product pages only (I can see images on the Home page). All other things on the frontend work good. My server settings meets Magento 2 requirements (php 7.1).
Prior to 2.3 version, I installed Magento 1.9.4 at the same server and everything worked good including admin dashboard.
I have tried few solutions that I found on this forum and some other but it didn't help.
I removed var/cache folder and executed the command below through CLI but nothing changed:
php bin/magento setup:static-content:deploy -f
How to solve this?
Thanks!
It's my first time with Magento shop. I try to install it on my web server (shared hosting) and got blank page with little grey stripe on the top.
My steps:
Download ZIP file with Magento
upload package on my web serwer via FTP
open URL with magento setup
Got blank page (screen below)
I was trying magento 2.3 with PHP 7.2 or Magento 2.2 with PHP 7.1 and also few other configurations. Always the same problem: blank page with grey tripe on the top. Where can be problem? Hosting provider told me that there is no errors, but maybe Magento need something more. Someone told me that Magento need at least 512MB of memory, so I made changes in php.ini file even to 756 and nothing...
No PHP errors. In /var/log/debug.log I have this mesages:
[2019-01-28 23:14:15] main.ERROR: Error: Application is not installed yet. [] []
You have to install Magento either by CLI or webinterface.
follow these official instructions
https://devdocs.magento.com/guides/v2.3/install-gde/install-roadmap_part1.html
I am trying to install vanilla magento 1.8.1.0 on a fresh new server, but after installation, on every admin page I go, I have to refresh the page twice to load it correctly.
When I just click on a link, only the header loads (without menubar) and the body is empty. If I refresh the page, it looks correctly. This happens sometimes on the front-end also, but happens always on the admin backend.
I have installed PHP 5.5 with OPCache on nginx on Ubuntu 13.10 server. There are no themes or plugins or any products created yet.
Any Ideas why this is happening?
Thanks,
Navneet
First click on the link -
*****Then I refresh the page to load it correctly *****
The problem was that php5-json module was not installed on the server. With previous version of PHP it was installed by default, but not anymore.
There is a simple fix to it -
apt-get install php5-json
Hope this helps anybody else who ran into same issues while clean installing a server with all latest releases.
Google App Engine recently added support for modules. And I'm almost certain I remember someone saying you can have modules with different runtimes. Your default app can be Python and a module could be in Java or PHP for example. And the module configuration file does make you specify the runtime for that module.
So why then can I not figure out how to run a PHP module inside a Python app?
I have a dispatch.yaml that contains:
dispatch:
- url: "*/blog*"
module: blog
And a blog.yaml for the module which contains:
module: blog
version: wp
runtime: php
api_version: 1
and a bunch of handlers for Wordpress.
Has anyone else been able to do this successfully?
In this case I want to run a wordpress blog under http:/www.domain.com/blog instead of under a sub-domain for SEO reasons.
It seems the appengine SDK is not using the module because if I try to go to /blog it just gives me a 404 error.
I'll continue to play with this and post an update if I find a solution.
I have everything working now. Google fixed some issues in version 1.8.5 making this possible. It's actually not that hard, you just have to remember to run appcfg.py update_dispatch in order to make the dispatch routing live. And also when deploying do appcfg.py update app.yaml wordpress.yaml
That way both configurations are uploaded and deployed.
Currently git push to deploy is still broken and in order to upload images wordpress wp-admin has to be running on the appspot.com domain which is not too big of a deal.
I wrote a blog post describing everything that I did to make it work:
http://blog.artooro.com/2013/10/09/run-wordpress-as-a-module-on-google-app-engine/