I've recently moved my working site to a staging environment, and now, some channels display an internal server error (500) while others work flawlessly. Nothing appears to have changed.
Is there some setting I've missed or might this have to do with a different PHP version on the staging server? Something else?
Edit 9/21:
I think I've narrowed it down to a CE_Image issue...it occurs on every template using CE_Image
Here's an example of some template code that, if removed, causes the errors to go away:
{cf_home_slideshow limit="5"}
<li data-slide="slide_{row_count}" style="background-image: url({exp:ce_img:pair allow_scale_larger="yes" src="{cf_image}" max_width="956" max_height="429" create_tag="no" crop="yes"}{made}{/exp:ce_img:pair})">
<img src="{exp:ce_img:pair allow_scale_larger="yes" src="{cf_image}" max_width="956" max_height="429" create_tag="no" crop="yes"}{made}{/exp:ce_img:pair}" width="956" height="429" />
<div class="slide">
{if cf_link}
<div class="view_project">
View Project <img src="/assets/imgs/arrow_btn.png">
</div>
{/if}
</div>
</li>
{/cf_home_slideshow}
D'oh! Resolved.
GD Library wasn't installed. When I installed it, all was well!
Related
Can anyone help me how to solve error of <main id="main" class=""> on google page speed.
Here is screenshot for the errors.
Website link is https://www.kritarthhandicrafts.com/
Try the following:
<main id="main">
Because you're not using any classes, there's no need to set the class attribute, and thus you should remove it.
I am trying to add buttons to my Spartacus storefront.
The problem that is preventing me to progress ahead is:
1)If I generate new button angular component, using Angular, should it be mentioned inside the
tag or outside of that?
2)Should it be rendered in a different way as first?
Check out this repo and the corresponding stackblitz project. The easiest way add new buttons would be to place it in reference to an existing standard component using the outlets. Essentially, you could do some like the following, placing your new angular component app-custom-component before the ExistingComponent.
<ng-template cxOutletRef="ExistingComponent" cxOutletPos="before">
<app-custom-component></app-custom-component>
</ng-template>
Can you describe the problem more clearly? As much as I understood you are looking for below kind of code. For code check this link Spartacus Product Page
<div class="row">
<div class="col-md-6">
<button
class="btn btn-block btn-action"
(click)="addAddressButtonHandle()"
>
{{ 'addressBook.addNewAddress' | cxTranslate }}
</button>
</div>
</div>
I´m working in a Windows App but when I want to add a toolTip I get this exception: HierarchyRequestError. I´ve checked if all my tags are properly typed and it seems that there is no problem with them. Any ideas?
<div id="wrapper" data-win-control="WinJS.UI.Tooltip" data-win-options="{contentElement:'info'}">
<img src="images/news.jpg" alt="Donald Trump">
</div>
<section class="info-wrapper">
<div id="info">
<video controls src="videos/info.wmv"></video>
</div>
</section>
Nevermind, I can´t use a dash. I changed it for an underscore and it worked.
I have the following code
<div id="navbar" class="collapse navbar-collapse">
<ul class="nav navbar-nav">
{exp:channel:entries channel="static" sort="asc" dynamic="off"}
<li>{title}</li>
{/exp:channel:entries}
</ul>
</div><!--/.nav-collapse -->
Which is looping through a channel I have for static pages on my website. Technically it is showing all the stuff it should do. This is the code it outputs:
<div id="navbar" class="collapse navbar-collapse">
<ul class="nav navbar-nav">
<li>Small Builders</li>
</ul>
</div>
However, when I click the link it gives me a white page. I have the htaccess from the documentation set up. I'm new to ExpressionEngine. Am I missing something completely obvious? I just want to link the the entry I've created.
If you try to go to abc.com/index/small-builders does it work? (added index)
I don't know if you're hiding index in the url or not but that can cause it.
The way I fixed this was the enable the Pages plugin on ExpressionEngine. Where I'm using ExpressionEngine 3.0.5 the plugin isn't installed/activated by default like it is on EE2.
Once this was activated I was able to assign templates and url structure no problem.
guess your post would be better on the expressionengine.stackexchange.com site.
Post it there and i´ll have a look if i can explain this to you
I have a site that was built and handed over to me, so I'm not as familiar with ModX as I'd like to be. That said, I've built my own templates, tpls and the like.
However, and existing MIGX using template is giving me fits. It used to display all the items in the list properly - one image, and three text fields. Now, it randomly will stop displaying one item.
When I say random, I don't mean that it switches around when you refresh the page - I mean right now item #4 isn't being displayed (even in source code, nothing appears). But if I were to delete any other item, that #4 might just show up again, and a different item start disappearing.
I'm at a loss here. I see no special characters in the text fields. Even if there were, that wouldn't explain how an item will work then not work then work again based on making changes to other items.
Please let me know what other information I can provide to assist in troubleshooting this.
Below is all the relevant code I can think of.
Template:
<div id="content">
[[!getImageList?
&tvname=`management`
&docid=`[[*id]]`
&tpl=`management_tpl`
&limit=`0`
]]
<div class="clear"></div>
</div><!-- #content -->
management_tpl:
<div class="management_box">
<div class="management_img">
<img src="[[+image:phpthumbof=`w=100&z=1`]]" alt="[[+pagetitle]]" />
</div>
<div class="management_content">
<h2>[[+name]]</h2>
<h3>[[+position]]</h3>
[[+descr]]
Show more
</div>
<div id="[[+name:stripString=` `]]" class="fulldescr">
<img src="[[+image:phpthumbof=`w=100&z=1`]]" alt="[[+pagetitle]]" />
<h2>[[+name]]</h2>
<h3>[[+position]]</h3>
[[+fulldescr]]
</div>
<div class="clear"></div>
</div>
Thanks,
Chris
For anyone who finds this in the future - my MIGX plugin was outdated and had some flaws that caused this. Updating the plugin fixed everything.