Magento2: [Magento 2.1.0] Catalog nav bar is missing in 2.1.0

[Ctucker9233]

Steps to reproduce

1. Put store in maitenance mode
2. Install Magento 2.1.0 from .zip folder per magento documentation
3. run setup:upgrade and setup:di:compile commands
4. Navigate to front end
   

   Expected result

Store page displays normally with catalog navigation

Actual result

Store page displays without catalog navigation

Note: Multi-store setup

[acidreian666]

what did you upgrade from?
is your Storefront using SSL aka (https://)
Are you running Varnish?
Theres simular issues going around.

[JDavidVR]

I have same problem upgrading from 2.0.7 to 2.1 I don't know why, probably its an issue with changes to the settings, before 2.1 it was on store>configuration>design, now it is on content > theme(or something like that)

[Ctucker9233]

@acidreian666 I upgraded from 2.0.7 and it uses SSL. I don't use varnish.

[Ctucker9233]

@JDavidVR It would seem that my theme is working ok. I didn't manipulate anything having to do with that nav bar.

[Ctucker9233]

If themes can't transfer from 2.0.7 to 2.1, that is a critical oversight.

[Ctucker9233]

If I clear /var/cache, /var/page_cache and /var/generation according to the documentation, http://devdocs.magento.com/guides/v2.1/comp-mgr/cli/cli-upgrade.html, this happens:

Warning: ltrim() expects parameter 1 to be string, object given in /home/tuckersf/public_html/vendor/magento/framework/Code/Generator/EntityAbstract.php on line 152

Notice: Uninitialized string offset: 0 in /home/tuckersf/public_html/vendor/magento/framework/Autoload/ClassLoaderWrapper.php on line 81

Notice: Uninitialized string offset: 0 in /home/tuckersf/public_html/vendor/composer/ClassLoader.php on line 317

Notice: Uninitialized string offset: 0 in /home/tuckersf/public_html/vendor/composer/ClassLoader.php on line 349
An error has happened during application run. See exception log for details.

[acidreian666]

So I been trying to Replicate the original problem my tests have been as fallowed.
Test 1
Install magento on Ubuntu 16.04 server w/ Nginx php7.0-fpm varnish mysql
installed magento2 to html dir
via
sudo wget magento2.1.zip (from official magento website)
then installed m2.1 via website installer http://localhost/setup/
no issues.

Finished install = Functional 2.1 with _NO_ menu on Homepage no matter what configurations are used.

Test 2
Installed Magento 2 Stack via Bitnami on Debain server.
m2.0.7 with apache mysql php7 varnish memcached ect.. basic stuff.
after using and making sure basic configuration is set and m2.0.7 is functional via http://localhost/
using Admin backend System Upgrade and upgrading to 2.1 upgrades flawlessly.
Finished install = Functional 2.1 _with_ menu on Homepage (Menus are working Functionally)
*Note
Using Varnish w/ Apache & m2.1 with SSL menu disappears the same way as it does using Test1.

Thoughts.
Issues with Nginx server using 2.1 compatibility?
Issues using the Official Magento2.1 zip from website?
Or could it be because of Debain jesse vs Ubuntu 16.04?

I'm going to do more testing.

[JDavidVR]

@Ctucker9233 I did more tests, trying to change configuration on backend and I agree with you this is a critical issue, for sites that are already build on 2.0.x and want to upgrade to 2.1

In logs I have this error:
[2016-07-03 23:08:39] main.INFO: Cache file with merged layout: LAYOUT_frontend_STORE1_2c7461af04bb11fe209659d7147d2c579 and handles default, cms_index_index, cms_page_view, cms_index_index_id_home: Please correct the XML data and try again. [] []
[2016-07-03 23:08:39] main.INFO: Cache file with merged layout: LAYOUT_frontend_STORE1_20a98983867a1770682b48d9a0ad63441 and handles 1column: Please correct the XML data and try again. [] []
[2016-07-03 23:08:39] main.CRITICAL: Broken reference: the 'currency' element cannot be added as child to 'header.panel', because the latter doesn't exist [] []
[2016-07-03 23:08:39] main.CRITICAL: Broken reference: the 'catalog.compare.sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-07-03 23:08:39] main.CRITICAL: Broken reference: the 'sale.reorder.sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-07-03 23:08:39] main.CRITICAL: Broken reference: the 'wishlist_sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-07-03 23:08:39] main.CRITICAL: Broken reference: the 'header.links' element cannot be added as child to 'header.panel', because the latter doesn't exist [] []
[2016-07-03 23:08:39] main.CRITICAL: Broken reference: the 'paypal.partner.right.logo' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-07-03 23:08:39] main.CRITICAL: Broken reference: the 'bml.right.logo' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-07-03 23:08:39] main.CRITICAL: Broken reference: the 'currency' tries to reorder itself towards 'store_language', but their parents are different: 'header.panel' and '' respectively. [] []
[2016-07-03 23:08:39] main.CRITICAL: Broken reference: the 'store.settings.currency' tries to reorder itself towards 'store_language', but their parents are different: 'store.settings' and '' respectively. [] []
[2016-07-03 23:08:39] main.INFO: Cache file with merged layout: LAYOUT_frontend_STORE1_26f1b068ec7ccf4878f9284dd1137afd1 and handles catalog_product_prices: Please correct the XML data and try again. [] []
[2016-07-03 23:08:43] main.INFO: Cache file with merged layout: LAYOUT_frontend_STORE1_22b24c6d6a5609522924195bc1e69d26e and handles default, not_noroute_other: Please correct the XML data and try again. [] []
[2016-07-03 23:08:44] main.INFO: Cache file with merged layout: LAYOUT_frontend_STORE1_20a98983867a1770682b48d9a0ad63441 and handles 1column: Please correct the XML data and try again. [] []
[2016-07-03 23:08:44] main.CRITICAL: Broken reference: the 'currency' element cannot be added as child to 'header.panel', because the latter doesn't exist [] []
[2016-07-03 23:08:44] main.CRITICAL: Broken reference: the 'catalog.compare.sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-07-03 23:08:44] main.CRITICAL: Broken reference: the 'sale.reorder.sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-07-03 23:08:44] main.CRITICAL: Broken reference: the 'wishlist_sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-07-03 23:08:44] main.CRITICAL: Broken reference: the 'header.links' element cannot be added as child to 'header.panel', because the latter doesn't exist [] []
[2016-07-03 23:08:44] main.CRITICAL: Broken reference: the 'currency' tries to reorder itself towards 'store_language', but their parents are different: 'header.panel' and '' respectively. [] []
[2016-07-03 23:08:44] main.CRITICAL: Broken reference: the 'store.settings.currency' tries to reorder itself towards 'store_language', but their parents are different: 'store.settings' and '' respectively. [] []
[2016-07-03 23:08:44] main.INFO: Cache file with merged layout: LAYOUT_frontend_STORE1_26f1b068ec7ccf4878f9284dd1137afd1 and handles catalog_product_prices: Please correct the XML data and try again. [] []

[Ctucker9233]

@JDavidVR Thanks for testing this out. So am I screwed and just need to do a clean install of 2.0.7?

[Ctucker9233]

@JDavidVR where did you find that log? Do you think there is a way to programatically fixing this?
@magento-team please investigate this.

[erikhansen]

I'm also experiencing this issue. I upgraded Magento Enterprise 2.0.7 to 2.1. I changed the theme to the Magento/luma theme and am still not seeing the main navigation. I _am_ using Varnish. I logged a similar issue for 2.0.x, but it was marked as fixed in 2.1: https://github.com/magento/magento2/issues/3897#issuecomment-219215906

[pboisvert]

Olena--can you have the team check this scenario?

[Ctucker9233]

@tkacheva In my scenario, I am not using varnish unless it got switched on without me knowing. It wouldn't surprise me at this point. How would I make sure that varnish is not running?

[Ctucker9233]

I've created my own menu as a sort of work around. Just buttons with straight links. I would still like to see this fixed as soon as possible. If it is a glitch with the upgrade procedure, the official documentation needs to change. That's what I used to arrive at this point. I can't continue to use Magento if I need to do a wipe, install new version and reimport data every time there is an upgrade. It is just not feasible.

[acidreian666]

Alright guys i have like 10 Magento 2 servers running on google cloud.
I figured out where the menu bar went well actually idk what code is stoping it from loading but...
ssh'd to my website root Dir
sudo cd /var/www/html/
run
sudo find . -type d -exec chmod 777 {} \;
&
sudo find . -type f -exec chmod 777 {} \;

Now menu is back and all permissions are messed up but its back and functional..

so where is the exact permissions required for every folder in a based 2.1 install?

[tkacheva]

@eug123 Could you look into it?

[Ctucker9233]

@acidreian666 So it's a permissions thing? Can you tell which folder is causing the problem? My site is live so I'd rather not change the permissions for every folder. It might be a security risk. Thanks for taking the time to really investigate this.

[Ctucker9233]

@tkacheva or @eug123 Is there any update on a timeline for this being fixed?

[acidreian666]

@Ctucker9233 so I have found that my sever with
m2.1
varnish4.1
nginx-latest U
buntu 16.04
mysql-latest
php7.0.8-fpm
Permissions all = 777 files & folders of /var/www/html/
functions perfectly untill I listen to port 443 and attempted to view the site in https://example.com then the menu navigation is gone. So then using nginx-latest to reverse proxy SSL termination it opens the site and leaves things broken and not responsive. Example still no menu in https and also now no menu in http either like it was before. Ex.2 adding to cart after product search also broken. List gos and gos.but I think that aside has more to do with SSL proxy & varnish.

Also I might add I have never switched from default mode to developer or production. But I did flush cache and reindex and static deploy manually.

[Ctucker9233]

@tkacheva @eug123 Any new information on this issue?

[Ctucker9233]

@tkacheva @eug123 @magento-team Is there any news on this issue? It is really effecting customer experience.

[JDavidVR]

I'm having this problem even in clean installation :(

[acidreian666]

@JDavidVR please list your full server setup & distribution information with components your using. I have installed and setup m21 10 times in the past 4 days with a functional navigation bar.

[Ctucker9233]

@acidreian666 On any of your setups did you install 2.0.7 and then upgrade to 2.1.0? I think this is where the problem really lies.

I'm hosted on siteground.com
Apache (not sure which version)
mysql (latest)
PHP version 5.6.23
Magento 2.1.0

I've flushed all caches repeatedly. The only thing I haven't tried is to set permissions on everything to 777 like you did. I don't know if that is safe to do.

[acidreian666]

@Ctucker9233 Are you using Varnish or Memcached or something simular or a cloudflare or Maxcdn?
I have never used Php 5.6 because theres 30x faster speed when using php7 from my expirence.

here is the question flushing the caches meaning your running the site in Devoloper mode not production?

have you tried
sudo rm -r pub/static/*
sudo php bin/magento setup:static-content:deploy

http://devdocs.magento.com/guides/v2.0/config-guide/bootstrap/magento-modes.html

I did 1 upgrade from 2.0.7 without a problem and multiple upgrades from 2.0.6 to 2.1 without problems.
but that was only with fixing permissions.

I think after your upgrade from 2.0.7 the System upgrade does not keep permissions on the deployed files or something in the theme that causes a permission issue. thus the menu is gone.

if you had your website up and running on a cloud server or something it would be abit easier to clone it and change domain to an Ip addess using mysql commands then changing permissions to 777 to check if thats the issue your having with your offical site.

[JDavidVR]

@acidreian666 I found something weird.
the first time, y copied files from magento 2.1 to 2.0.7 (both with sample data) but it gave me the catalog nav error, so I tried to copy again the files(it overwirte 2.0.7) but still it was not working.
at the end I did a rm -rf vendor/* and copied a clean vendor folder from 2.1, and it solved the problem, I don't know exactly which files are different.

about clean installation, I applied same solution and it worked, I have to mention that first installation worked well, but I think a deploy messed files, becuase I'm using phpstorm to deploy files to my local web server(I'm using virtualbox to have latest version of php7.0.x , apache2.4.x and mysql 5.6.x)

@Ctucker9233 can you apply the steps I mentioned, so you can confirm or discard if it is working (it worked for me) if it works, means that magento 2.0.7 contains files that was discarded in 2.1 and it is causing conflicts.

[tkacheva]

Issue MAGETWO-55189.

[Ctucker9233]

@acidreian666 I've never changed the magento mode as far as I know. I only use a straight forward static cache, nothing more. When I say that I've flushed the caches, I've manually deleted the folders within pub/static/frontend, var/cache and var/page_cache. Siteground also has it's own button to flush static cache files so I do that too just to make sure it's all clean.

@JDavidVR I'll be darned. Your solution did the trick. That means there's an old file somewhere causing a conflict. Thanks a ton!

[Ctucker9233]

@veloraven @tkacheva Thanks for your responsiveness! Is there a way I can follow this internal ticket? Any ideas when a permanent fix will be released? I know you're all working on a million other things so I appreciate any updates you can give me.

[piotrekkaminski]

@JDavidVR it seems as if you attempted to overwrite files. This is incorrect approach to upgrade as it will not remove files that could be removed in new version, and it will cause issues. The proper upgrade path is either using command line or setup wizard, which allows to remove files that were removed in new version.

[Ctucker9233]

@piotrekkaminski I also tried this approach and this is why the issue exists. At the time it was the only upgrade option available to me. Setup wizard did not function (even with the 2.0.7 patch) and the CLI kept throwing a memory exceeded error. I've gone back and forth with my hosting provider on this one.

My point is, if for some reason both of the approved upgrade methods are unusable, overwriting files is the only option and there should be a way to do that without errors like this occuring. Perhaps including text in the changelog or release notes on what files need to be permanently deleted in order to have a functioning setup.

[dman311]

I'm also having the same issue with the menu not appearing. I upgraded from 2.0.7 to 2.1.0, at first the upgrade would not proceed. I was able to remove the migration tool and the upgrade appeared to be successful. I am not able to see products on the front end and I get a server error on the back end when trying to view categories. I'm going to pull a backup and go back to 2.0.7 until this issues is resolved.

[sebastian-ehrling]

delete the directory "vendor". Then reinstall vendor directory from zip!

[HellgaM]

I have a custom theme, adding of " " to block with name="store.menu" in my theme did the trick.

[tkacheva]

@dman311
@JDavidVR
guys, does anyone have this issue when upgrading using setup tool or command line?

[alyzrazor]

I think I found the cause for this bug, I tried to reproduce this problem in many different ways and scenarios using fresh installations of 2.1, PHP 5.6 or 7, once I change from http to https my nav bar is gone in HOME, but it works in some other places like: Account Login etc...

It ONLY happened as SOON AS I ACTIVATE VARNISH, so it doesn't happen when I'm using Built-in Cache

[Ctucker9233]

@tkacheva My issue occurred after command line upgrade.

@alyzrazor I am the original poster of this issue and I DO NOT USE VARNISH. I never switched from http to https either. So it does not only happen under these conditions.

[karlsminton]

I also am experiencing this issue, I'm using no caching extensions - just inbuilt.
I also upgraded via commandline, one of the recommended methods and I'm not presently using https.

[Ctucker9233]

@karlsminton have you tried deleting the entire vendor folder and reloading a fresh 2.1 vendor folder?

[karlsminton]

@Ctucker9233 I'm reluctant to do this if it can be avoided, for the reasons piotrekkaminski mentioned earlier.

[tkacheva]

@Ctucker9233, if you still have this issue with CLI upgrade, please provide detailed steps end environment you are using so that we are able to reproduce the case. We managed to reproduce the issue only with direct override the files which is not the right way to upgrade.

[Ctucker9233]

@tkacheva I followed the Magento documentation on how to upgrade (which has a 404 error right now by the way.).
So perhaps there is a lack of clarity in the documentation or failure to understand on my part. From what I recall, it says to unzip and extract the upgrade to the Magento root (which starts to overwrite files, so not sure how to get around that.). I drag and drop the .zip and extract all. Next it says to enter the CLI command php bin/magento setup:upgrade, which runs and completes successfully. I use putty to ssh in and run CLI commands. Next, I'm prompted to rerun the compile command. So I type in php bin/magento setup:di:compile. These are the exact same steps I provided in the original post for this issue.
Now, given that removing the vendor folder and re-uploading using FTP solved the issue, there was probably a file that did not get overwritten during the install and caused a dependency issue. It may be all mute now, since 2.1.1 has been released and the error has not re-occurred.
The reason I installed this way was because I don't have access to composer commands or don't know the correct syntax to use them. Plus, the system upgrade feature was broken at the time, so this was the only option left. So even though it may not have been the correct procedure, it was the only option available and in the end it worked.
I think the documentation needs to be more detailed with exact steps for each upgrade method. Otherwise, some of us are left guessing on how to do it properly.

[Ctucker9233]

@tkacheva Sorry forgot to include the environment. It was Magento 2.0.7 upgraded to 2.1.0. php version 5.6.23. I don't know the mySQL version. It's a hosted server with siteground.

[flipflap]

I have the same problem after updating from 2.0.9 to 2.1.0 using composer.

Now I tried to upload the directory vendor from zip and get an error:

`a:4:{i:0;s:273:"Please upgrade your database: Run "bin/magento setup:upgrade" from the Magento root directory.
The following modules are outdated:
Magento_Sales schema: current version - 2.0.3, required version - 2.0.2
Magento_Sales data: current version - 2.0.3, required version - 2.0.2";i:1;s:2816:"#0 /home/preview1/public_html/vendor/magento/framework/Interception/Chain/Chain.php(67): Magento\Framework\Module\Plugin\DbStatusValidator->aroundDispatch(Object(Magento\Framework\App\FrontController\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))

1 /home/preview1/public_html/vendor/magento/framework/Interception/Chain/Chain.php(63): Magento\Framework\Interception\Chain\Chain->invokeNext('Magento\Framewo...', 'dispatch', Object(Magento\Framework\App\FrontController\Interceptor), Array, 'front-controlle...')

2 /home/preview1/public_html/vendor/magento/module-page-cache/Model/App/FrontController/BuiltinPlugin.php(73): Magento\Framework\Interception\Chain\Chain->Magento\Framework\Interception\Chain{closure}(Object(Magento\Framework\App\Request\Http))

3 /home/preview1/public_html/vendor/magento/framework/Interception/Chain/Chain.php(67): Magento\PageCache\Model\App\FrontController\BuiltinPlugin->aroundDispatch(Object(Magento\Framework\App\FrontController\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))

4 /home/preview1/public_html/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Framework\Interception\Chain\Chain->invokeNext('Magento\Framewo...', 'dispatch', Object(Magento\Framework\App\FrontController\Interceptor), Array, 'front-controlle...')

5 /home/preview1/public_html/vendor/magento/module-page-cache/Model/App/FrontController/VarnishPlugin.php(55): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception{closure}(Object(Magento\Framework\App\Request\Http))

6 /home/preview1/public_html/vendor/magento/framework/Interception/Interceptor.php(142): Magento\PageCache\Model\App\FrontController\VarnishPlugin->aroundDispatch(Object(Magento\Framework\App\FrontController\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))

7 /home/preview1/public_html/var/generation/Magento/Framework/App/FrontController/Interceptor.php(26): Magento\Framework\App\FrontController\Interceptor->___callPlugins('dispatch', Array, Array)

8 /home/preview1/public_html/vendor/magento/framework/App/Http.php(135): Magento\Framework\App\FrontController\Interceptor->dispatch(Object(Magento\Framework\App\Request\Http))

9 /home/preview1/public_html/vendor/magento/framework/Interception/Interceptor.php(146): Magento\Framework\App\Http->launch()

10 /home/preview1/public_html/var/generation/Magento/Framework/App/Http/Interceptor.php(26): Magento\Framework\App\Http\Interceptor->___callPlugins('launch', Array, Array)

11 /home/preview1/public_html/vendor/magento/framework/App/Bootstrap.php(258): Magento\Framework\App\Http\Interceptor->launch()

12 /home/preview1/public_html/index.php(39): Magento\Framework\App\Bootstrap->run(Object(Magento\Framework\App\Http\Interceptor))

13 {main}";s:3:"url";s:1:"/";s:11:"script_name";s:10:"/index.php";}`

bin/magento setup:upgrade did not help.

@HellgaM can you explain in which files you made this changes? I don't have that block store.menu.

[Ctucker9233]

@flipflap I had to physically delete the vendor folder using FTP and physically reload it. Then I reran bin/magento setup:upgrade with no problem. Not sure if this will help in your case. Magento frowns on this method, but it was the only thing that solved the problem.

[flipflap]

@flipflap I tried this, but got the errors. Did you use the new vendor folder from the zip?

[KevinMace]

I have recently been having the issue that when Varnish was enabled, the menu (topNav block) didn't appear.

What I discovered was Varnish wasn't parsing the ESI tags, instead they were output to the frontend. In your source code search for a snippet like the following:

<esi:include src="url/of/your/site" />

If you find any "esi" tags on your page, then your Varnish config is incorrect and needs to be updated to enable "esi". After I updated my Varnish config to enable esi, everything started working as expected and the menu re-appeared.

[flipflap]

I don't have Varnish on my server, that can't be the reason in my case.

[flipflap]

I updated to 2.1.1 but still had the same problem. Now I found out that the problem comes from this code in my theme:

<container name="header.panel.wrapper" htmlClass="panel wrapper" htmlId="stopbar" htmlTag="div" before="-"/>

I need to add an id stopbar to the div panel wraper. Now I tried to move top.links but it didn't work. Finaly I add the ID by Javascript.

[KevinMace]

@flipflap have you checked your source code for the ESI tags? Magento might still be generating those tags and without Varnish you will have a missing nav.

[tkacheva]

@Ctucker9233
here is the CLI upgrade guide http://devdocs.magento.com/guides/v2.1/comp-mgr/cli/cli-upgrade.html
please help us to improve it by referring to particularly confusing points.

[OmarFaruque]

i am facing same problem :\

[rqsakai]

I Had de exactly same issue, but on the tests i realized that it was due to a custom plugin i made for the GTM (Google tag manager).

I inserted a block on the category and product page from the xml like this:
<block ifconfig="gtm/config/enabled" class="Dufry\Gtm\Block\Product" before='GTM' name="Datalayer" template="Dufry_Gtm::datalayer.phtml"/>

And every ESI block after it failed to work, when i removed it i got it back working, but I still need this block for marketing purposes.

So I added the no cache tag to the block, but the entire page won't be cached, so i doesn't work.

Than I added the TTL, it works but i can't get the current category/product, I tried doing: $this->getProduct() and form the Magento\Framework\Registry, and it always return null no matter what

So i still need to fix this issue, but the menu is back working.

Hope it helps

[Ctucker9233]

@tkacheva I would recommend clarifying what "Installed the compressed archive" means with some steps on how to install the compressed archive correctly. Then, I would recommend having two sections on how to upgrade using CLI. One for if you do it with composer and one for if you do it with the compressed archive. Right now, I only see the section for doing it with composer. Since I don't have access to composer, I can only do it with the compressed archive. I was left scratching my head on how to do it with the compressed archive. Hope this helps and let me know if I need to clarify anything.

[Ctucker9233]

@tkacheva I can work on creating a pull request for the docs if you like. Or is it better if I let you and the magento team handle it?

[Microstudioweb]

Hi, I have same issue with catalog nav bar.
I have also update magento from 2.0.7 to 2.0.8 to 2.0.9 to 2.1.0 to 2.1.1 but the issue remain.
Try to change file permission, upload vendor's folder, Install Magento 2.1.1 as new installation.

But the only difference is that I can see the catalog nav bar only when I'm on catalogs pages

and this message on home page:
_We're sorry, an error has occurred while generating this email._

It is annoying to have issues on each update
Somebody have a solution for this issue?

[OmarFaruque]

I solve my nav error using fresh installation Magento 2.1.1 with sample
data.

On Tue, Oct 11, 2016 at 10:19 PM, Microstudioweb [email protected]
wrote:

Hi, I have same issue with catalog nav bar.
I have also update magento from 2.0.7 to 2.0.8 to 2.0.9 to 2.1.0 to 2.1.1
but the issue remain.
Try to change file permission, upload vendor's folder, Install Magento
2.1.1 as new installation.

But the only difference is that I can see the catalog nav bar only when
I'm on catalogs pages

and this message on home page:
_We're sorry, an error has occurred while generating this email._

It is annoying to have issues on each update
Somebody have a solution for this issue?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/magento/magento2/issues/5423#issuecomment-252967030,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGBi5EXncLD7Q2mD5nhrNFJpNs-1xDAjks5qy7cUgaJpZM4JDz3z
.

---

Best Regards
Omar Faruque https://www.facebook.com/profile.php?id=100006084726970
_Web Analyst_
Green Dot Limited http://greendotbd.com/ & ABM Water Company
http://www.abmwater.com/
House # 135, Road # 05, Mohakhali DOHS, Dhaka.

[Microstudioweb]

@OmarFaruque Unfortunaly I have tried a fresh installation 2 times, but it didn't get effect.

I find this code:

_public function filter($value)
{
    try {
        $value = parent::filter($value);
    } catch (\Exception $e) {
        // Since a single instance of this class can be used to filter content multiple times, reset callbacks to
        // prevent callbacks running for unrelated content (e.g., email subject and email body)
        $this->resetAfterFilterCallbacks();            if ($this->_appState->getMode() == \Magento\Framework\App\State::MODE_DEVELOPER) {
            $value = sprintf(__('Error filtering template: %s'), $e->getMessage());
        } else {
            $value = __("We're sorry, an error has occurred while generating this email.");
        }
        $this->_logger->critical($e);
    }
    return $value;
}_

on {{magento-folder-root}}/vendor/magento/module-email/Model/Template/Filter.php

I suspect the issue is because it didn't find parent::filter($value); on homepage, but when is on category page it find out.

[OmarFaruque]

Are u install it using command or browser? I install my magento using commend line

[Microstudioweb]

@OmarFaruque I had install via browser.

UberTheme on magento community post a workaround that fix this issue, here you can see how fix it:
https://community.magento.com/t5/Installing-Magento-2/After-Migration-Products-not-showing-on-Frontend/td-p/42005

[OmarFaruque]

Thanks i will see :)

[Ctucker9233]

@tkacheva The steps as far as I can tell to upgrade using the compressed .zip file are as follows...

1. download compressed .zip archive
2. move compressed .zip archive to server root folder (public_html) where magento 2 is installed.
3. open CLI and login as user with root privileges
4. run command cd in my case, public_html
5. run command unzip This begins to unzip the file and replace files with the same name
6. run command php bin/magento setup:upgrade
7. run command php bin/magento setup:di:compile
8. In web browser navigate to backend and frontend to ensure upgrade completed successfully

I just followed these steps to upgrade to 2.1.2 and it worked flawlessly. I think these steps should be included in the devdocs as a way to upgrade using the command line without composer.

[dunarri]

I am seeing this issue as well on a clean install.
Setup details:
Clean install from 2.1 zip file.
PHP 7.0.11 via FPM
Apache 2.4
Using Varnish
No https
Multi-store (3 stores)

I've observed the problem only happens with the other stores that are not the default. Default store works fine. And it only happens when varnish FPC is enabled, if I disable FPC in the Magento admin all 3 stores work just fine. So it seems to be an issue caching the topnav block for store codes other than default. I've also noted that when I try to load one of the other stores with the missing category nav, I get errors in my log file that are almost identical to what @JDavidVR reported on Jul 3.

[timstoel]

I am having this issue as well. We had a staging server with Ubuntu 16.04, Apache2.4.18, PHP 7.0.8 and MariaDB 10.0.27. It was first installed from a zip file using the web interface as Magento 2.0.7 and then was upgraded to 2.1.1. This server is showing the menu on the home page properly.

We are almost ready to launch so I moved the files and database from that Magento install to a production server with Ubuntu 16.04, Nginx 1.10.0 Varnish 4.1.1, PHP 7.0.8 and MariaDB 10.0.27 on a separate server. The menu disappeared on the home page, and I ended up here :)

If I turn off FPC in the admin, the menu comes back. Turn it back on, and it is gone again.

Someone here [https://github.com/magento/magento2/issues/3897#issuecomment-219215906] suggested adding this to the Varnish config as a workaround:
-p feature=+esi_ignore_https \

But this did not solve the problem. Another thread suggested replacing /vendor/* with fresh files from the 2.1.1 zip file but I have not tried that yet.

[craigcarnell]

I have the same issue, clean install of 2.1.2 using the LUMA theme. Varnish 4.1.3, PHP 7.0.12.

Happens to me on OSX and Ubuntu 16.04

[2016-11-04 09:48:36] main.INFO: Cache file with merged layout: LAYOUT_adminhtml_STORE1_391fccd54da687afc76a5d6559b714906 and handles default, adminhtml_dashboard_index: Please correct the XML data and try again.  [] []
[2016-11-04 09:48:36] main.INFO: Cache file with merged layout: LAYOUT_adminhtml_STORE1_3cf9ab1b1723bedc1dcd665a812b00335 and handles admin-1column: Please correct the XML data and try again.  [] []
[2016-11-04 09:48:36] main.CRITICAL: Broken reference: the 'header' tries to reorder itself towards 'global.notices', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2016-11-04 09:48:36] main.CRITICAL: Broken reference: the 'page.breadcrumbs' tries to reorder itself towards 'notifications', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2016-11-04 09:48:36] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and 'header' respectively. [] []
[2016-11-04 09:53:38] main.INFO: Cache file with merged layout: LAYOUT_frontend_STORE1_2c7461af04bb11fe209659d7147d2c579 and handles default, cms_index_index, cms_page_view, cms_index_index_id_home: Please correct the XML data and try again.  [] []
[2016-11-04 09:53:38] main.INFO: Cache file with merged layout: LAYOUT_frontend_STORE1_20a98983867a1770682b48d9a0ad63441 and handles 1column: Please correct the XML data and try again.  [] []
[2016-11-04 09:53:38] main.CRITICAL: Broken reference: the 'catalog.compare.sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-11-04 09:53:38] main.CRITICAL: Broken reference: the 'sale.reorder.sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-11-04 09:53:38] main.CRITICAL: Broken reference: the 'wishlist_sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-11-04 09:53:38] main.CRITICAL: Broken reference: the 'paypal.partner.right.logo' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-11-04 09:53:38] main.CRITICAL: Broken reference: the 'bml.right.logo' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []
[2016-11-04 09:53:38] main.INFO: Cache file with merged layout: LAYOUT_frontend_STORE1_26f1b068ec7ccf4878f9284dd1137afd1 and handles catalog_product_prices: Please correct the XML data and try again.  [] []
[2016-11-04 09:54:45] main.INFO: Cache file with merged layout: LAYOUT_adminhtml_STORE1_3c4aeb00db6a394ed5a76424a54e4bfd3 and handles default, adminhtml_system_config_edit: Please correct the XML data and try again.  [] []
[2016-11-04 09:54:45] main.INFO: Cache file with merged layout: LAYOUT_adminhtml_STORE1_3793edbdc1c00dd1c3aa9e1b3dc856b39 and handles admin-2columns-left: Please correct the XML data and try again.  [] []
[2016-11-04 09:54:45] main.CRITICAL: Broken reference: the 'header' tries to reorder itself towards 'global.notices', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2016-11-04 09:54:45] main.CRITICAL: Broken reference: the 'page.breadcrumbs' tries to reorder itself towards 'notifications', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2016-11-04 09:54:45] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and 'header' respectively. [] []
[2016-11-04 09:54:45] main.INFO: Cache file with merged layout: LAYOUT_adminhtml_STORE1_36f1b068ec7ccf4878f9284dd1137afd1 and handles catalog_product_prices: Please correct the XML data and try again.  [] []
[2016-11-04 09:54:45] main.INFO: Item Magento_Backend::system_currency was removed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::system_design_schedule was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::system_store was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::dashboard was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::system was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::system_tools was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::system_design was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::system_convert was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::system_cache was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::marketing was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::marketing_communications was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::marketing_seo was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::marketing_user_content was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::content was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::content_elements was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::stores was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::stores_settings was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::stores_attributes was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::other_settings was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::system_other_settings was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backend::setup_wizard was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Backup::system_tools_backup was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Theme::design_config was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Theme::system_design_theme was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Customer::customer was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Customer::customer_manage was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Customer::customer_online was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Customer::customer_group was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_AdminNotification::system_adminnotification was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Indexer::system_index was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Cms::cms_page was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Cms::cms_block was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Catalog::catalog was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Catalog::catalog_products was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Catalog::catalog_categories was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Catalog::catalog_attributes_attributes was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Catalog::catalog_attributes_sets was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Catalog::inventory was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Search::search_terms was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Search::search_synonyms was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Widget::cms_widget_instance was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_CheckoutAgreements::sales_checkoutagreement was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Config::system_config was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_CurrencySymbol::system_currency was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_CurrencySymbol::system_currency_rates was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_CurrencySymbol::system_currency_symbols was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Downloadable::report_products_downloads was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_ImportExport::system_convert_import was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_ImportExport::system_convert_export was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_ImportExport::system_convert_history was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Email::template was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_User::system_acl was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_User::system_acl_users was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_User::system_acl_roles was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_User::system_acl_locks was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Sales::sales was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Sales::sales_operation was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Sales::sales_order was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Sales::sales_invoice was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Sales::sales_shipment was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Sales::sales_creditmemo was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Sales::sales_transactions was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Sales::system_order_statuses was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Marketplace::partners was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_CatalogRule::promo was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_CatalogRule::promo_catalog was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Newsletter::newsletter_template was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Newsletter::newsletter_queue was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Newsletter::newsletter_subscriber was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Newsletter::newsletter_problem was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_SalesRule::promo_quote was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Paypal::report_salesroot_paypal_settlement_reports was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Paypal::paypal_billing_agreement was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_marketing was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_salesroot was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_salesroot_sales was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_salesroot_tax was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_salesroot_invoiced was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_salesroot_shipping was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_salesroot_refunded was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_salesroot_coupons was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_shopcart_product was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_shopcart_abandoned was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_products was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_products_bestsellers was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_products_sold was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_products_viewed was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_products_lowstock was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_customers was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_customers_accounts was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_customers_totals was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_customers_orders was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_statistics was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Reports::report_statistics_refresh was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Search::report_search_term was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Review::catalog_reviews_ratings_ratings was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Review::catalog_reviews_ratings_reviews_all was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Review::report_review was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Review::report_review_customer was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Review::report_review_product was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Integration::system_extensions was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Integration::system_integrations was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Sitemap::catalog_sitemap was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Tax::sales_tax was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Tax::sales_tax_rules was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Tax::sales_tax_rates was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_TaxImportExport::system_convert_tax was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_UrlRewrite::urlrewrite was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_EncryptionKey::system_crypt_key was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Variable::system_variable was processed [] []
[2016-11-04 09:54:45] main.INFO: Add of item with id Magento_Braintree::settlement_report was processed [] []
[2016-11-04 09:54:45] main.INFO: Remove on item with id Magento_Backend::setup_wizard was processed [] []
[2016-11-04 09:56:25] main.CRITICAL: Broken reference: the 'header' tries to reorder itself towards 'global.notices', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2016-11-04 09:56:25] main.CRITICAL: Broken reference: the 'page.breadcrumbs' tries to reorder itself towards 'notifications', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2016-11-04 09:56:25] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and 'header' respectively. [] []
[2016-11-04 09:56:45] main.CRITICAL: Broken reference: the 'header' tries to reorder itself towards 'global.notices', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2016-11-04 09:56:45] main.CRITICAL: Broken reference: the 'page.breadcrumbs' tries to reorder itself towards 'notifications', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2016-11-04 09:56:45] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and 'header' respectively. [] []

[ooples]

I'm having this same issue as well. I notice that in the admin settings it gives you the option between built in cache and varnish cache and it says that varnish is recommended so I'm wondering why if this seems to be such a common issue.

[Tristan-N]

@Ctucker9233 I have the same issue, using Magento 2.1.2 on PHP 7.0.14 on Apache server.

When I switch to Built-In cache, the navbar appears again. When I found the rule like @KevinMace mentioned, I noticed that my URL contained a lot of %22 signs, instead of the " symbol.

<esi:include src="http://site.url.here/page_cache/block/esi/blocks/[%22catalog.topnav%22]/handles/[%22default%22,%22catalog_category_view%22,%22catalog_category_view_type_layered%22,%22catalog_category_view_type_layered_without_children%22,%22catalog_category_view_id_688%22,%22catalog_category_view_layout_update_ba80f00be44c0fe6892e24d5b04c895d%22]/" /></div>

Now figuring out how to solve this. If somebody knows something, please let me know. Otherwise, I hope this helps some people out while they're debugging.

[KevinMace]

@Tristan-N Have you enabled ESI in your Varnish config? That will replace this string

<esi:include src="http://site.url.here/page_cache/block/esi/blocks/[%22catalog.topnav%22]/handles/[%22default%22,%22catalog_category_view%22,%22catalog_category_view_type_layered%22,%22catalog_category_view_type_layered_without_children%22,%22catalog_category_view_id_688%22,%22catalog_category_view_layout_update_ba80f00be44c0fe6892e24d5b04c895d%22]/" /

with the correct content (in this instance, the navigation)

[KevinMace]

@Tristan-N in your default.vcl, you should have a section like below. Have you moved the Magento generated .vcl in to your server's Varnish directory?

if (beresp.http.content-type ~ "text") { set beresp.do_esi = true; }

[Tristan-N]

@KevinMace No, in the Varnish config folder there is a config file dat includes the vcl file from the Magento folder.

[Jilco]

@KevinMace have you already figured out how to do this? Or anybody else? I'm facing the same issues afte migration from 1.9.2.4 to 2.1.3. The navigation bar is missing, also with a normal HTTP request. I'm not able to modify varnish settings in Core Magento, or am I wrong? Magento is using a build in version of Varnish in my understanding.

[joe2010]

i have the same problemas download magento 2.1.3 set it all up and no top nav

https://community.magento.com/t5/Theming-Layout-Design-Questions/magento-2-ver-2-1-3-Category-not-showing-up-in-nav/m-p/56191/highlight/false#M866

[plhbbillygarcia]

Hello does anyone have any solutions to the above. I am at my wits end with 2.1. I am managing a project with over 5000 items and my clients work flow is halted because of this navigation search bar issue. We moved from 1.9 to 2.1.2 5.7 for MYSQL and 5.6.5 for PHP. We are so upset with this new version.. Any help would be great.

[timstoel]

The solution is staying on Magento 1.9 and waiting it out on Magento 2. We spent a lot of time and money on Magento 2 and had to roll back to 1.9.

[plhbbillygarcia]

Yes I wish.... But the investment on my clients end is too deep. We can't role back now. The team that is working on this are having a hard time and I am as well.. Can anyone give me an idea of how to approach a solution. I have a team that can build what is needed but they need direction. We are far too into this with all variables and can't hit brakes... I would like to help write code to fix this stupid shit somehow... Thank you all for reading and hopefully writing..
Smiles
Billy

[Jilco]

I removed the TTL attribute from /vendor/magento/module-theme/view/frontend/layout/default.xml and the menu bar was there again! But can that do any harm, if I'm correct the default TTL is enheritated. Or am I wrong?

Regards Jilco

Verzonden vanaf mijn Samsung-apparaat

-------- Oorspronkelijk bericht --------
Van: plhbbillygarcia [e-mail]
Datum: 24-01-2017 04:05 (GMT+01:00)
Aan: magento/magento2 [e-mail]
Cc: Jilco [e-mail], Comment [e-mail]
Onderwerp: Re: [magento/magento2] [Magento 2.1.0] Catalog nav bar is missing in 2.1.0 (#5423)

Yes I wish.... But the investment on my clients end is too deep. We can't role back now. The team that is working on this are having a hard time and I am as well.. Can anyone give me an idea of how to approach a solution. I have a team that can build what is needed but they need direction. We are far too into this with all variables and can hit brakes... I would like to help write code to fix this stupid shit somehow... Thank you all for reading and hopefully writing..
Smiles
Billy

-
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/magento/magento2/issues/5423#issuecomment-274688678, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWoMGm9YgFaGYbygl-QVZayLZNTtDMykks5rVWqIgaJpZM4JDz3z.

[timstoel]

@plhbbillygarcia Unfortunately Magento 2 is just not production ready. I would imagine by the time your client pays to fix everything that is broken, Magento 2 will be further along. I can't see taking a lone ranger type mission on trying to fix the many, many issues with Magento 2. It sounds like your client has an unrealistic expectation for Magento 2 at this time and you may need to educate them on the issues at hand.

[dvershinin]

To anyone experiencing this issue with Varnish and already added -p feature=+esi_ignore_https to your Varnish configuration, the following are correct steps to fix:

1. enable developer mode in Magento
2. enable display of PHP error logs, if that is disabled system wide (php_admin_value)
3. navigate to your page and identify the PHP fatal error in place of navigation area
4. edit corresponding PHP file to fix.

In my case error was with Magestore Giftvoucher plugin.

Basically a fatal PHP error may occur only while Varnish is in use (ESI processing) and may not be experience otherwise. Not all the plugins are Varnish-ready.

[mttjohnson]

@dvershinin
To add some additional options to use when checking for Varnish specific issues and ESI includes I have found it useful to use curl to simulate a specific backend request from Varnish.

I have a gist with some example commands, and brief comments.

Using varnishlog you can see all the necessary header information you'd need to makes calls to the backend HTTP server the same way Varnish is, and then set the HTTP header details with curl on the command line.

This can provide some additional insight to what Varnish is receiving, or trying to request before it removes headers, combines ESI includes, and responds to the browser. It can also be useful to test the infrastructure behind Varnish and know you aren't getting a cached hit from Varnish, or have to clear the Varnish cache.

[shoaibrehman]

Hey guys,

I had the same issue with one of my clients and after going through this entire thread here, I can conclude that it is the varnish configuration issue.

I spoke to my hosting company and they confirmed that Varnish was only configured to support HTTP requests. They configured varnish for HTTPS as well and everything is working fine now.

[dunarri]

I've circled back to this after installing the latest Magento 2.1.5 and it would appear it is resolved.

[rgoncharuk]

@Ctucker9233 internal MAGETWO-55189 closed as Won`t Fix. As I understood you agreed that the upgrade way mentioned in the description can not be used. Improvements into documentation can be created as PR to https://github.com/magento/devdocs Feel free to connect the Community Engineering team for support on that PR

[Ctucker9233]

@rgoncharuk Thanks, although that is disappointing to hear. It is clear that other people that have commented on this thread have a similar issue and it clearly is not a documentation issue. I have since resolved the issue by separating my multi-site into two independent ones. If nothing else, the documentation for setting up multi-sites should be reviewed and revised by the Magento Team seeing as how you(Magento) created it and not me.

[moejoee91]

Hello everyone,
im having something similar to this and it's driving me crazy, all of a sudden my nav-bar was gone, and im not even using varnish, i'm using the built in cache, all i did right before this happened is i did setup cloudflare and it went down hill from there
any ideas what might be causing the problem ?

[Ctucker9233]

@moejoee91 Try disabling Cloudflare and see if it changes anything.

[AdamReece-WebBox]

This still doesn't work today. I've tried:

• Removal of all cache folder content (pub/static, var/cache, var/generation, var/page_cache, and var/view_preprocessed)
• Removal of all vendor folder content
• composer update
• php bin/magento setup:upgrade
• php bin/magento setup:di:compile
• php bin/magento setup:static-content:deploy

All ran successfully, but still no navbar.

It appears that ESI tags are not being processed, which is required for the navbar.

This is on a cPanel based hosting account without any Varnish caching. (Magento 2.1.8, PHP 7.0.31)

[dvershinin]

@AdamReece-WebBox in absence of Varnish, nothing can do ESI processing on a cPanel server.

[AdamReece-WebBox]

Hi @dvershinin,

It appears that the agency that gave us the project to deploy didn't tell us that Varnish cache was enabled in Magento's settings.

Switching this to use Magento's built-in cache resolved the issue. (ESIs process as intended now.)

[ftudlong]

But can you switch back to varnish after resolving the issue?

[AdamReece-WebBox]

Would there be much benefit in that? I don't really want to disrupt a live store, particularly as it's already performing very well with the built in cache.