#43707 closed defect (bug) (invalid)
Why Using Un-nacessory file(JS & CSS)
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 5.1 |
| Component: | Query | Keywords: | |
| Focuses: | javascript | Cc: |
Description
Hello Sir/Madam,
I have request you please remove the un-usable js and css file, so these file creating a problem our custom code, they conflict our custom websites, so there no using file so please remove the un-usable file, i request you again.
One more suggestion, i have create a new user particular email address but i have can't understand who is login current time of my wordpress.
Redesign the dashboard as like attached screenshot.
Thanks
Mohit
Wordpress Developer
Attachments (1)
Change History (3)
Note: See
TracTickets for help on using
tickets.
WordPress is a framework, which contains certain functionality as a common service to plugins and themes, so that there won't be any needed for each plugin and/or theme to include this functionality inside their own code structure. See, for example, https://codex.wordpress.org/Javascript_Reference for more detailed information about this.
Further, bear in mind that one important design principle for WordPress is backward compatibility. If a function was available for plugin developers in previous WordPress releases, then it will in almost all cases remain being available. If it has been moved to the collection of deprecated functions, then warnings will be visible during debugging, but in most situations the functions will still continue to work. The idea around this is that upgrading to the latest WordPress release should in virtually all cases be a smooth process. A downside of this is that you have to keep some deprecated code in the package.
For a more detailed reply, please indicate what specific files you think are not needed.
I don't understand your second question at all. But I have a feeling that a better place for that topic would be in the support forums at https://wordpress.org/support
Your proposed dashboard design looks like the result of using WordPress as a framework for a web application. That is a perfectly valid way of using WordPress, but the task oriented view you're implying in your proposal has really no bearing at all for a plain WordPress installation. ("Tasks" is not available as a content type in a basic WordPress install.)
I'll close this ticket as invalid, since it contains no clear bug description or suggestion.
You may reopen the ticket if I misunderstood you.
However, in general, try to have only one main topic in each ticket.