3

Instead of duplicating the entries, you could run your entries loop twice (or as many times as you want) maybe? {% for i in 0..1 %} {% for entry in entries %} {{ entry.title }} <br> {% endfor %} {% endfor %}


2

You should replace postCategories with whatever the handle of the category field is for your entry.


2

You can't access date this way, you'd need to use the date (docs) or datetime (docs) or even atom (docs) filters. In the case of your report, since you have multiple conditions, you would need to pass those as an array and use the atom filter. Try: {% set purchases = purchases .postDate([ 'and', '>=' ~ settings.datetimeStartDate|atom, ...


2

I was able to fix this on my local MAMP installation by following the instructions for making MAMP play nicely with Craft in this guide, then executing the command chmod a+x craft from this tutorial.


1

I think I figured out the problem. This was my first time switching to the project.yaml configuration Deleting and rebuilding the project config allowed me to change the Commerce > System Settings > Email > Language which fixed the error.


1

Sorted YAY! In case this is helpful to anyone, I tried deleting and reinstalling via composer then replacing the config and .env files but no luck there so I downloaded the latest version and updated just the vendor folder. It needed to update the database which it couldn't do for me so I took a manual backup and let it do it's thing and now it's all ...


1

Allright, after digging & debugging a bit further into this issue I found it out myself! $event->sender->addErrors([ 'expiryDate' => Template::raw('<a href='.$entry[0]->cpEditUrl.'>'.$entry[0]->title.'</a>') ]); PS: don't forget to add this to the top of your php file: use craft\helpers\Template;


1

It turned out that RewriteBase / needed to be added to the htaccess


1

I restarted my DB server and it fixed the issue. Sorry for the false alarm, but I've never seen something like that before. Should have tried the DB restart before.


1

Errors for the users/save-user action are recorded against the user object, not the session object. If the user is logged-out, the object is named user but if they are logged-in you must use currentUser. Generally speaking you can retrieve errors from Yii objects in several ways, but for field-by-field errors, I prefer the simplicity of getFirstError() (You ...


1

Thank you Oli for helping with this simple quest. Here's the code that worked for me. ("decade" being the name of the field I'm using in the backend, putting out the category group!) {% for category in entry.decade.all() %} <a href="{{ category.url }}""> {{- category.title -}} </a> {% endfor %} {% endif %}


1

Have a look at your .env file on the production system and your config/db.php file your repo. Craft has changed the way db access data is stored and must now be provided as a DSN This is now config/db.php return [ 'dsn' => getenv('DB_DSN'), 'user' => getenv('DB_USER'), 'password' => getenv('DB_PASSWORD'), 'schema' => getenv('...


1

From Craft Support: Assuming the credentials in your .env are correct on that site, could you run ./craft clear-caches/all (or manually empty your web/cpresources and storage/runtime


1

But is the issue related to the size of the Matrix Field? Or overall the number of fields in the database? Neither. :) That error message isn't related to the linked Github issue (although I can see how you'd get them confused). It's coming from the Craft's Plain Text field type: https://github.com/craftcms/cms/blob/develop/src/fields/PlainText.php#L126-...


1

I ended up uploading the files to my own hosting environment where I updated it to the latest version of Craft and plugins etc. Then pulled down locally and it worked fine.


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