Tips for getting forum questions answered

This is a community-contributed tutorial. This tutorial is over a year old and may not apply to your version of Concrete CMS.
Mar 30, 2016
By MrKDilkington for Editors, Designers, Developers
Edit

Questions that are clearly written and include specific details have the best chance of being answered by community members. To prevent duplicate questions from being asked, please search the forum, documentation, and tutorials for an answer first.

1. Have you included a question with specific details including:

  • What is the problem?
  • When did the problem start?
  • Did the problem start after a certain action or event?
    Examples:
    switching themes, changing theme CSS, adding theme JavaScript, modifying code in files, adding a custom block, installing an add-on, upgrading Concrete CMS, moving your site to a new server
  • What are the steps to reproduce the problem?
  • What are you trying to accomplish?
    • What is the expected result?
    • What is the result you are getting?

2. Have you cleared your concrete cache?

Dashboard > System & Settings > Optimization > Clear Cache

3. Have you cleared your browser cache?

4. What version of concrete and PHP are you using?

Version information for concrete and PHP can be found on the Environment Information page:
Dashboard > System & Settings > Environment > Environment Information

  • Core Version
  • Version Installed
  • PHP Version

5. What operating system, browser, and browser version are you using?

6. What theme are you using?

Is it a custom theme or a theme from the marketplace?

7. What is the address of your website?

8. Are you receiving an error message?

9. Are there errors in your browser console?

http://documentation.concretecms.org/tutorials/how-open-browser-console-view-errors

10. If you are receiving an error:

Include the location of the error and the page it was on. Copy and paste the full error inside [code] tags. Placing errors inside [code][/code] tags keeps the original error formatting and allows for quicker inspection.

Example:

[code]
your error message
[/code]

11. Include screenshots and screen recordings:

Taking a picture or video recording of your screen assists others in identifying the problem you are having. It is especially helpful for questions that you may have a hard time explaining with words.

Free screenshot and screen recording software is available for Windows, OSX, and Linux.

Recent Tutorials
Customize locale icons
Oct 29, 2024
By myq.

How to customize locale (language region) flags

Concrete CMS Caching Guide
Oct 16, 2024
By lemonbrain.

An overview of types of caching in Concrete and considerations when using them.

Redirect all requests to HTTPS
Oct 9, 2024
By myq.

How to follow best practices for a secure web

Upgrade Concrete versions 9.3.1 and 9.3.2
Sep 10, 2024
By myq.

How to get past a bug in versions 9.3.1 and 9.3.2 that prevents upgrading the Concrete core through the Dashboard

How to use Composer with Marketplace extensions
Aug 22, 2024
By PortlandLabs.

Composer can be used to manage third-party extensions from the marketplace

Controlling Google Tag Manager Tags Based on Concrete CMS Edit Toolbar Visibility
Aug 13, 2024
By jessicadunbar.

This document provides a step-by-step guide on how to control the firing of Google Tag Manager (GTM) tags based on the visibility of the Concrete CMS edit toolbar. It explains how to create a custom JavaScript variable in GTM to detect whether the edit toolbar is present on a page and how to set up a trigger that ensures GTM tags only fire when the toolbar is not visible. This setup is particularly useful for developers and marketers who want to ensure that tracking and analytics tags are not activated during content editing sessions, thereby preserving the accuracy of data collected.

Improvements?

Let us know by posting here.