Make WordPress Core

Opened 3 years ago

Closed 3 years ago

#53703 closed feature request (invalid)

still in same path but need to be cloud ready

Reported by: cadentic2018's profile cadentic2018 Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: General Keywords:
Focuses: Cc:



it is a quite long time now everything is going well but still, everyone is on the same path.

  1. no aws elasticsearch support for WordPress core. simply these searching methods are too old Magento core giving it out of the box at free of cost .
  2. address autocomplete with google geocode API
  3. no re: definition towards the cloud-friendly environment
  4. no Cognito integration methodology
  5. too many plugins conflict with others issue persists for end-user
  6. all plugin vendors are opt-in forcibly after installation which is annoying and simply it is a compromisation of privacy for the site owner.
  7. people are not looking for WordPress for a one-pager they are spending money on hosting it so it must be considered with a guideline while plugin authors will be submitting their code to the WordPress repo.

8.for one-pager there are lots of options at a bare minimum cost but WordPress must focus more than that.

so when ?

Change History (1)

#1 @desrosj
3 years ago

  • Keywords needs-privacy-review removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed
  • Version 5.8 deleted

Hi @cadentic2018,

Welcome to Trac!

I'm not really sure what the goal of this ticket is. There are 8 separate and unique points with no specific changes requested or suggestions made.

If you have specific requests for changes to WordPress that can make it easier for you to accomplish something specific, please open one ticket per request.

Note: See TracTickets for help on using tickets.