Hot answers tagged

8

Found the fix. https://support.ellislab.com/bugs/detail/20152 Edit system/expressionengine/helpers/segment_helper.php around line 97 to add this conditional above ee()->load->model(‘category_model’); so it looks like: if (empty($category_name)) { return ''; } ee()->load->model('category_model');


6

Stash 2.5.3 will stop this error notice with EE 2.8.x The problem was: in EE 2.8 the Template::advanced_conditionals() method assumes that the Template::$layout_conditionals array exists, even if your template does not make use of the new 'layouts' feature. Is that a bug for Ellislab to fix? Arguably, yes. Stash v2.5.3 adds a workaround for this problem, ...


5

Have you checked all of your installed add-ons for updated versions? White screens are also typically a sign of hidden errors, so make sure that display_errors is enabled in your PHP environment, and set the $debug value in the admin.php file to 1. That may reveal a PHP error that identifies the problem. If that doesn't help, and you think you have the ...


5

The grid field is a looping field, so if the field is in fact called beneficiaries, you should have: {beneficiaries} {beneficiaries:total_rows} {beneficiaries:field_total_rows} {/beneficiaries}


4

I finally found out that Structure 3.3.1 is the culprit when you set it to redirect to Structure on login. You can get past it by editing the config file and change $config['allow_extensions'] = 'y'; to $config['allow_extensions'] = 'n';


4

There’s a Javascript bug in EE 2.8.0 that breaks the field settings page and other areas of the CP when certain add-ons are installed, including Matrix. It’ll be fixed in 2.8.1, and EllisLab has posted a patch file here: https://support.ellislab.com/bugs/detail/20165


4

If your {exp:stash:get_list} tag is wrapped by another tag pair, then commonly used template variables like no_results are parsed for the parent tag by EE. Add the prefix="my_prefix" parameter to provide a namespace, and use the prefix like this: {if my_prefix:no_results}...{/if} There are a few other ways to check that a list exists (or is empty): With ...


4

I think you'll find switching to a multi-environment config file a more convenient alternative than using an add-on for updating paths after migration (eg dev to staging to production). The really nice thing about using config overrides this way is that there is usually zero configuration update needed when migrating. One excellent, widely used and well-...


3

If you get in touch with Travis at Structure, there's a BETA which will resolve the 'redirect to structure on login' with 2.8x.


3

This turned out to be a bug when Tag is used with other addons that add cache variables to the Sessions object before it actually exists. A workaround for the issue will be in Tag 4.2.7, which we are testing for release.


2

I got this issue after upgrading to 2.8.1 from 2.7.3 I had Stash installed, but only got this error one one template that didn't use Stash. I got this error on a page that had Switchee. Then inside the default Case of Switchee, I had Croxton's IfElse running around an advanced conditional. I removed the IfElse tags around the advanced conditional and the ...


2

We ran into this issue and it ended up being related to Stash. I'd start there if you have it installed.


2

Try to disable one by one your modules, addons and analyse the results after disabled each one.


2

When I've come across similar issues it's been down to the contents of config.php. Check what $config['app_version'] = ''; is set to. It should match the version of EE that is currently installed when you run the installer (2.5.2 in your case). When it's been set to a different version (sometimes because the config files has been copied across from another ...


2

I know this one was very obscure and thereby avoided by most readers, but in the event that anyone out there has the same experience, here is the solution. There were several add-ons that reference /expressionengine/libraries/services_json.php in EE 2.5.5, including Freeform and devot:ee monitor. I had to update these modules to the latest releases BEFORE ...


2

It turned out that a rogue index.html file with a redirect inside was the issue. <title>Redirect</title> <meta http-equiv="refresh" content="0; url=index.php"> Everything hitting the root was being redirected so the ACTion ID's weren't able to process (which is pretty critical for Store payments to process). Removing this file resolved ...


2

Per the comments in the question you linked to, Store doesn't support mapped member fields during registration with Zoo Visitor (due to ZV not correctly handling member registration hooks). So your only option is to use the workaround in that thread, or craft your own workaround. Alternatively, as I mentioned in your last question, you can simply create a ...


2

The variables need to have a name and that url_title is a reserved word. To avoid conflicts, if you need to keep the Segments required set to no, keep a static part on the first segment: /{coaching_type:regex[(workplace|personal)]}-coaching/{coaching_title:alpha_dash} By this way, you can't grab the first segment by {segment:coaching_type}, but {segment_1}...


2

I'm using SuperSearch and getting the same issue, it appears that 'entry_id' is no longer being set in the settings array. I've fixed/patched for now by simply replacing line 2214 in the third_party_search_index() function which was $entry_id = $this->settings['entry_id']; To become: $entry_id = ee()->api_channel_entries->entry_id;


1

Reatile's answer is good for what you outlined in your question, but one possible consideration and possibly easier to implement is to make use of the {entry_id}. This automatically is a unique numerical value which increases by 1 every time a new entry is created. You could also prepend some other identifier like 'sku{entry_id}', which would then render ...


1

You could write an extension calling the ee()->extensions->call('channel_form_submit_entry_start', $this); http://ellislab.com/expressionengine/user-guide/development/extension_hooks/module/channel_form/index.html#channel-form-submit-entry-start In your extension you then do the unique (auto increment) value by using the DB class to check for ...


1

Just closing the loop. I did file a bug report here and it was accepted.


1

If the page is reloading there are a couple things that you should do. In the final step of your checkout process make sure that you have {error:payment_method} in your template (docs). Remove error_handling="inline" from the opening checkout tag on the last page this will show the default error page instead of putting things inline which would only show up ...


1

You shouldn't need to prefix with Playa for what you're doing. You should just be able to use... {exp:channel:entries...} {project_content} {content limit="1"} <h4><a href="/projects/{url_title}">{title}</a></h4> {/content} {/project_content} {/exp:channel:entries} The var_prefix parameter comes ...


1

That should be right - but you can check the source within the themes folder: /themes/javascript/compressed/jquery


1

IF you are using the register a member tags you need to make sure that you have either a username or email address field in your template populated and both a password and a password confirm field. Username is the users email address: {field:register_member} <label for="register_member">Register Member Account?</label> {!-- if you want people ...


1

This most likely means that one or several of the files in themes folder is not uploaded correctly. Re-upload themes folder and make sure the path and URL for themes folder are correct in EE preferences.


1

Newer versions of ee have more strict security requirements for post data. Try adding the following to your form: <input type="hidden" name="XID" value="{XID_HASH}" /> (This is an older question but I am adding this as it a common resolution to these sorts of problems.)


1

Some add-ons / field types in your Channel Form will only work if the JS is included in the head, which is unfortunate, as best-practice dictates your JS should live below the content. I worked around this by adding a parameter in my header/footer embeds called js_in_head. On pages with Channel Forms, I just included my main jQuery include in the header, ...


1

replace : $this->EE->pagination->get_template(); with: $this->EE->TMPL->tagdata = $this->EE->pagination->prepare($this->EE->TMPL->tagdata); Updates: I don't use Super search before, I just tell you what you must change. if you use $channel->pagination->get_template() then change it to $channel->pagination-&...


Only top voted, non community-wiki answers of a minimum length are eligible