Problem: Creating a new storeview does not seem to 'connect' it to the website view, and thus it doesn't inherit its configuration. Also see screenshots below to make things more clear.
Additional Information
Between the last storeview we created, and the new one (Test), no real changes were made to the codebase. The shop has been running on version 2.2 ever since and no new extensions were installed.
I've tried to verify several things, such as checking whether the store was correctly linked to the website (in database table "store"). I also came across a bug, that supposedly existed in version 2.1.3 (as seen in https://magento.stackexchange.com/questions/157925/magento-2-1-3-store-view-config-doesnt-inherit-website-config), I have verified that this fix is part of the code.
Saving the website config to hopefully overwrite the store config did not work, nor did flushing the entire cache (including cache on disk). No errors are shown in the logs whenever a new storeview is created or modified.
Below you can see a specific setting (it happens to ALL settings) in website view
And below what it looks like in the "Test" storeview
I'm a bit lost and not sure where to look anymore. Any help would be appreciated.
Related
A very annoying just surfaced. I did some database tweaking, migrated it and manually imported the user table together with some other tables.
Suddenly the home page of my laravel spark won't display properly. It automatically goes to the settings#/subscription page.
The routes are still intact but are the HomeController is not used at all. I've cleared all caches but still the same. No errors in the log.
And even more annoying as I just found out, it only affects existing users that I imported. New users are not affected. So it definitely has something to do with the MySQL import.
I already compared the users values of a new user and an old one and tried to mimick the new one as much as possible. Doesn't work.
Anyone have an idea how to solve this?
It's been a while so you probably got to the bottom of this, but I just ran into the same issue.
In my case, I installed Spark without the team flag and signed up. Later, I added the necessary code to add teams back in without migrating and seeding. In a few places in my code I'm running the teamSubscribed middleware, and that was the crux of my problem. The redirect started looking at the team subscription status instead of the user subscription status.
Since I didn't sign up as a team, those fields were null, and it redirected pages with the middleware.
For others that come across this:
Search your codebase for the middleware (likely either in a constructor or your routes).
Double check your database for the corresponding user or team active trial status.
This is for a client so I won't share exact domains but the problem is as follows..
I took over development of a website from a prior developer.
The hosting is Hostgator Business.
The primary domain is primary.com.
There is an addon domain addon.com.
The primary domain document root is /home1/username/public_html.
The addon's document root is /home1/username/addon.com.
www.addon.com had a WordPress installation which the developer had edited instead of using plugins to achieve his goals. The site also needed a complete redesign so I felt it logical to simply wipe the installation and replace it.
So, I deleted all of the WordPress files and uploaded a new copy of WordPress from wordpress.org/latest.tar.gz
Prior to deleting the old installation, the domain loaded files from it's document root perfectly.
After uploading the new installation instead of resolving to addon.com it is instead resolving to primary.com/addon.com
I've never seen this happen before so I'm lost.
There's no errors in any available logs.
All file permissions are correct.. I've triple-checked.
I've tried deleting all files and creating simple index.php and index.html files to see if it would access them ... it doesn't.
This happens in each browser I use on Windows and Linux.
I don't understand it because all I did was swap out the old WP install for a new one.
I went and re-uploaded the old WordPress installation so everything is 100% how it was but it is still going to primary.com/addon.com instead of addon.com.
Has anyone faced this issue before? I usually use Bluehost but even when I've used Hostgator in the past I've never seen this happen.
I double-checked the addon domain settings as well as anything else I could think of and everything appears normal.
I even deleted the addon domain and re-added it with the document root of /home1/username/addon.com and it still goes to primary.com/addon.com in the browser.
I submitted a ticket with Hostgator but they have not replied yet.
I'm sorry if this is long. This is my first time asking for help on here and I wanted to be sure I included everything I could.
Hostgator finally got back to me.
The previous developer had used the one-click WordPress install.
Apparently once someone uses a one-click install the only way it works is if you keep using the one-click install/you cannot do it manually any more.
From all the servers and sites I've setup this makes no sense and is a problem with Hostgator. Support did not really tell me anything other than "you have to use the one click install since the prior developer did". Great service.
Hope this saves someone some hassle.
From this it sounds like you were moving a WordPress site from the primary domain to an add on domain.
Simply moving the files from the primary to the add on domain will not make it work on the add on domain because in the database and throughout the coding of the WordPress site it would all be configured and coded for the primary domain.
It sounds like you would need to update the site home and site url from the primary to the add on domain url.
http://support.hostgator.com/articles/specialized-help/technical/wordpress/wordpress-home-fix
Also I would be suggest using a search and replace type plugin to go through all the internal coding to update the urls and links to the add on domain.
There is more information here as well http://codex.wordpress.org/Moving_WordPress
So I've gotten myself into a bit of a pickle and need assistance from StackOverflow Gods.
We're trying to transfer a Magento site from one server (Godaddy) to another (Private Virtual Server) for the purpose of becoming a test site.
I'm not familiar with Magento (my first mistake) but I researched migration, and I ran across an article that said all you need to transfer is the database, theme files, catalog files and skin files.
So that's just what we did. We setup a fresh install, added the files and the site (http://boulderfootandankle.com/apv-test/) looks like it's got some formatting errors. We figured we could fix those after adding the database.
As soon as we connected the database through the local.xml file, the theme changed to a generic one (I imagine a fallback) and we were locked out of the admin.
I tried a number of the solutions offered for this very problem, which included:
Clearing the var/cache and var/session folders.
Altering the core config data values for the unsecure and secure web base urls.
Deleting the unsecure and secure web base urls and cookie values form the database.
Changing the sessions save CDATA from "files" to "db"
Changing the install date to the original
Altering the varien file
...and nothing seems to work.
At this point, I'm just wondering if doing a fresh transfer of the site from one server to another, instead of transferring specific files into a fresh install, would work
Did you use the same encryption key as the previous installation? The encryption key is set in the local.xml file and needs to be the same on both extensions. When you did a fresh install it would have given you a new encryption key and this could be why you are unable to login.
just my quick list for transferring sites...
1. run files backup and mysql dump (from source)
2. Copy local.xml (from Target)
3. Restore backup and mysql dump (to Target)
4. Restore local.xml(from step 2 to Target)
5. Correct base_url (in Target)
The only time I have ever had a problem with this is when I run things locally for dev in that case there is varien specific check that monks with admin login(but, sounds like you know this).
https://magento.stackexchange.com/questions/26071/magento-1-9-can-t-login-to-admin-panel
I am on 1.14 and the posters suggestion essentially is the same fix I found. Of course the responder is totally correct on the horror of this solution but, since this is a test site as long as you leave yourself the right notes you should be able to undo this when you move to production.
I was wondering if anyone could help me with the following issue. On our Magento site, enterprise version 1.10.1.1, a user may log in, and it will say another person's name. Then, if you click on another link, it might go back to your name. The user sessions are clearly being confused. Apparently, this is a full-page caching problem, because our full page cache is often invalidated and, if we turn it off, the user sessions no longer mix up. However, turning it off considerably slows down the site. Switching the sessions from db storage to file storage (and vice versa) did not fix the issue. Does anyone know what the problem could be or how to solve it?
Thanks very much,
Brenda
You should check with Magento for a patch. I had a similar problem with Gift Certificate field info getting mixed up between sessions. They provided a patch that resolved the problem.
In the header.phtml file you should use this to print the user name
<?php echo $this->getChildHtml('welcome') ?>
Then, you can override the block 'Mage_Page_Block_Html_Welcome' if you wanna customize your message.
this happens when you use "Full Page Cache" because by default, magento exclude some blocks of the full page cache, and the block 'welcome' is one of they. if you are using customization code and message, the user name will be cached too, and other users will see different user names in this section.
it can be dependence on the cache issue. Try to turn cache off (go to admin, system, cache management and disable all cache).
If issue gone - you need to check cache configuration. If not - you have really session issue.
BTW, where you store sessions (files or DB or memcached?)
I found the cause related to Enterprise_PageCache_Model_Processor_Default class, my way is disable it in config.xml, edit src\app\code\core\Enterprise\PageCache\etc\config.xml:
<requests>
<!-- <cms>enterprise_pagecache/processor_default</cms>-->
</requests>
This problem was probably caused by Magento not being able to set proper session parameters if it was behind a reverse proxy cache like Varnish (I bet it was the case). Whenever using an intermediate caché system you have to make sure you are using the apropiate module in Apache to forward the X_FORWARDED_FOR http header to Magento like mod_rpaf, otherwise Magento will see al requests coming from the same IP and it will not be able to determine correct session isolation as it will think all requests come from the same client.
For some reason, when I log into my joomla 1.6 backend, it is now empty, displaying only a logout button. Any Ideas?
I just went through the same problem but on J!1.7.3. There may be many, many reasons but please check using just URL if you can see for example:
[YourDomainHere]/administrator/index.php?option=com_content or
[YourDomainHere]/administrator/index.php?option=com_modules
If content is listing and you're missing just Admin-menu and sub-navigation in back-end --> this means you messed-up with access levels and viewing access.
If you can't see content listing - ignore the rest of this post :-)
...with access levels and viewing access. To check that, try entering [YourDomainHere]/administrator/index.php?option=com_users&view=levels and enter each position in the list. Joomla backend navigation module usually has Access set to Special, so focus on this one. When enter Special - manager, author and super administrator should be ticked. If everything empty in any from the list - this is your issue :)
You need to add manager, author and super administrator to your Special access level. Obviously you can't see Save button, so you need to use database. [wrrr :) sounds scary?] Not a big deal, just go there using for example phpMyAdmin and find _viewlevels table. In there just edit Special and add [6,2,8] values to set up manager, author, super.....
Update database. Try to log-in one more time (close browser and clean cache before).
I hope if this wasn't helpful for you, will be for somebody else.
p.s. There may be a way of 'saving' changes in you joomla access levels with URL. Then you don't need to go to DB .. but I don't know if this is feasible at all :)
Check the rewrite of htaccess and the $mosConfig_absolute_path variable in config.php
Apparently, the Bluestork Template (admin template) has some security issues. In my case there were some missing files in the template folder /administrator/templates/bluestork/ that caused the administrator screen to appear blank. I've copied a clean version of the template in the bluestork folder and after that I was able to see the backend admin area.
I've removed the bluestork templates entirely for now, which seems to be the best option. Joomla installs 2.5.8, 2.5.6, 2.5.2, 1.7.0, 1.6.3 are affected. The Blustork Template is a target for hacks with old Joomla.
this happening becoz of admin user lost his permissions. see below article to fix this issue
http://www.codentalk.com/joomla-admin-showing-blank-page/