Feature suggestion: In-all as default mode

  • Resolved Won’tsharehere

    (@benosika)


    5 years, 8 months ago

    The default area-of-effect for each resource file is in-admin and not in-frontend.

    I suggest making a third mode which will be default — in-all.

    I think it will make the module more accessible by making to prevent a confusion like “I wrote my CSS/JS line but I can’t see any change” in the user-space while the admin doesn’t know that the module defaultly covers only admin pages.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Diana Burduja

    (@diana_burduja)

    5 years, 8 months ago

    Please use the designated terminology, otherwise we might not understand each other.

    I assume by “resource file” you mean “custom code”, by “area-of-effect” you mean the “Where in page” option, by “module” maybe you mean “plugin” (not sure), by “user-space” you mean “the frontend” and by the “admin page” you mean “the backend” …?

    The default value for the “Where on page” option is “In Frontend”, not “In Admin”, as you claim. Besides that I didn’t understand exactly what is the issue.

    • This reply was modified 5 years, 8 months ago by Diana Burduja.
    Thread Starter Won’tsharehere

    (@benosika)

    5 years, 8 months ago

    Basically you understand me fine, only this:

    area of effect -> frontend or backend.

    and sorry I confused frontend with backend in the end.

    Plugin Author Diana Burduja

    (@diana_burduja)

    5 years, 8 months ago

    I’ll propose the suggestion to my colleagues and let you know about it.

    Thread Starter Won’tsharehere

    (@benosika)

    5 years, 8 months ago

    Covered in the end → covered in the start… Sorry for the confusion. Awful period in my life… :///

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Feature suggestion: In-all as default mode’ is closed to new replies.