Oh, WOW....I should have disabled CSS bundling minification..maybe I would have also seen the problem!
Thanks a million!
That's a perfect solution.
Many thanks!
I have disabled CSS bundling.
Thanks for looking at it!
Hello-
We recently updated one of our plugins (other developer), and one of it's two views stopped re-sizing for different screen sizes. The plugin changed it's structure a little, but there are still just two main views, but now have some partial views called within them.
The problem seems to be the Side-2 class is not using the alternate stylesheets, like 480.css, etc..and keeps using the 220px definition from the main stylesheet, even when viewed with a smaller device...at least, that's what it SEEMS like...I don't know for sure. I've tried many things but cannot get it to look like it did before.
Here's a normal page on my site which behaves correctly:
http://www.myfootshop.com/shoe-insoles-and-arch-supports
This is the view from the plugin which is still responsive:
http://www.myfootshop.com/article/arthritis-of-the-foot-and-ankle
And here is the plugin view that is no longer responsive:
http://www.myfootshop.com/articles/List/2
Can you see a reason for this problem?
Thanks!
Hello-
I am adding our company logo to our main slider images, and I am wanting to stop the theme-defined logo from appearing on the home page ONLY.
I opened my /Views/Shared/_Root.cshtml and see this variable is defined:
isHomePage = true;
<div class="home-page-header main-slider-header">
@Html.Partial("Header")
</div>
@if (isHomePage)
{
@* do not show logo *@
}
else
{
<a href="@Url.RouteUrl("HomePage")" class="logo">
@if (!MvcHtmlString.IsNullOrEmpty(alfrescoLogo))
{
@alfrescoLogo
}
else
{
string storeName = EngineContext.Current.Resolve<IStoreContext>().CurrentStore.GetLocalized(x => x.Name);
<img title="" alt="@storeName" src="@Url.Content(logoPath)">
}
</a>
}
You're right. I didn't get the point. First you said "technical obstacle"...in my mind, obstacles must be leapt over, bypassed, or conquered. Then you said "technical problem"..problems are meant to be solved.
I initially tried to ask you what changesets to 3.50 were made that prevent you from being able to add the same functionality to 3.40 version of the plugin. In my mind, I do not see why I cannot implement whatever changes were made in 3.50 into my 3.40 version, which would then make it compatible with your newer version plugin...but you did not answer it.
I wish I could edit my replies.....
I don't mean to be obtuse, but my company needs this capability and I must endeavor to find a viable solution. Whatever the cost, and from whomever can provide it. If the version of the product I purchased from you (barely a year old) cannot be easily modified to include the same functionality as newer version, I understand...but it is almost impossible for me to believe that you guys are not capable of achieving it.
I'm fairly certain that your code is obfuscated, and therefore I wouldn't be able to provide another developer with the source code and hire them to make the modification. Right?
So, unless you guys can be contracted to make the modification for me, I must hire another developer to re-create the entire plugin for me....which I'll do if I have to.