3 Rewording attempt to have it consider for re-opening
source | link

How doescan I improve as a site builder effectively dealfor dealing with errors I don't know how to handle?

As a relatively new Site Builder, I understand some of what is going on under the hood. But when things go wrong…wrong .…

Without an intimate knowledge of module code and inner workings, the error messages often simply tell me something went wrong. 

Furthermore, I don’t know if a particular message occurred from the action I just executed, or haveif I have simply not been to a specific page in a while (or never before), in which case any number of actions could have broken it. 

In any case, I have no idea what messages like this one mean:

'Notice: Undefined index: var_name in _some_method_some_where() (line 35…'35 .…'

means.

MyThis are the steps I typically perform (my workflow) to resolve an error:

  • Check module issue queue for known bug – Occasionally I found a known problem.
  • Google the error – Normally this doesn’t help as the same error could happen for so many reasons, but occasionally it leads me to a fix.
  • Ask a developer if possible – they have no idea about my problems…
  • Ignore the error and keep working.
  • If my site is really broke, try to reset (ugh) or give up on the module altogether and do something else (sigh).
  1. Check the module's issue queue for known bugs – Occasionally I find a known problem.
  2. Google the error – Normally this doesn’t help as the same error could happen for so many reasons, but occasionally it leads me to a fix.
  3. Ask a developer if possible – They often have no idea about my problems …
  4. Ignore the error and keep working.
  5. If my site is really broken, I try to reset (ugh) or give up on the module altogether and do something else (sigh).

As a site builder, I really don't want to dive into the code every time.

How can I improve my workflow? Like what other steps, resources, approaches, etc would you recommend to a site builder when such kind of things go wrong?

How does a site builder effectively deal with errors?

As a relatively new Site Builder, I understand some of what is going on under the hood. But when things go wrong…

Without an intimate knowledge of module code and inner workings, the error messages simply tell me something went wrong. Furthermore, I don’t know if a particular message occurred from the action I just executed, or have I simply not been to a specific page in a while, in which case any number of actions could have broken it. In any case, I have no idea what

'Notice: Undefined index: var_name in _some_method_some_where() (line 35…'

means.

My workflow to resolve an error:

  • Check module issue queue for known bug – Occasionally I found a known problem.
  • Google the error – Normally this doesn’t help as the same error could happen for so many reasons, but occasionally it leads me to a fix.
  • Ask a developer if possible – they have no idea about my problems…
  • Ignore the error and keep working.
  • If my site is really broke, try to reset (ugh) or give up on the module altogether and do something else (sigh).

I really don't want to dive into the code every time.

How can I improve my workflow?

How can I improve as a site builder for dealing with errors I don't know how to handle?

As a relatively new Site Builder, I understand some of what is going on under the hood. But when things go wrong .…

Without an intimate knowledge of module code and inner workings, the error messages often simply tell me something went wrong. 

Furthermore, I don’t know if a particular message occurred from the action I just executed, or if I have simply not been to a specific page in a while (or never before), in which case any number of actions could have broken it. 

In any case, I have no idea what messages like this one mean:

'Notice: Undefined index: var_name in _some_method_some_where() (line 35 .…'

This are the steps I typically perform (my workflow) to resolve an error:

  1. Check the module's issue queue for known bugs – Occasionally I find a known problem.
  2. Google the error – Normally this doesn’t help as the same error could happen for so many reasons, but occasionally it leads me to a fix.
  3. Ask a developer if possible – They often have no idea about my problems …
  4. Ignore the error and keep working.
  5. If my site is really broken, I try to reset (ugh) or give up on the module altogether and do something else (sigh).

As a site builder, I really don't want to dive into the code every time.

How can I improve my workflow? Like what other steps, resources, approaches, etc would you recommend to a site builder when such kind of things go wrong?

    Post Closed as "primarily opinion-based" by kiamlaluno
2 edited tags
| link
1
source | link

How does a site builder effectively deal with errors?

As a relatively new Site Builder, I understand some of what is going on under the hood. But when things go wrong…

Without an intimate knowledge of module code and inner workings, the error messages simply tell me something went wrong. Furthermore, I don’t know if a particular message occurred from the action I just executed, or have I simply not been to a specific page in a while, in which case any number of actions could have broken it. In any case, I have no idea what

'Notice: Undefined index: var_name in _some_method_some_where() (line 35…'

means.

My workflow to resolve an error:

  • Check module issue queue for known bug – Occasionally I found a known problem.
  • Google the error – Normally this doesn’t help as the same error could happen for so many reasons, but occasionally it leads me to a fix.
  • Ask a developer if possible – they have no idea about my problems…
  • Ignore the error and keep working.
  • If my site is really broke, try to reset (ugh) or give up on the module altogether and do something else (sigh).

I really don't want to dive into the code every time.

How can I improve my workflow?