ClassicPress: The CMS for Creators. Stable. Secure. Instantly Familiar.

Related tags

CMS php classicpress
Overview

ClassicPress: The CMS for Creators. Stable. Secure. Instantly Familiar.

ClassicPress is a community-led open source content management system for creators. It is a fork of WordPress 4.9 that preserves the TinyMCE classic editor as the default option. It is more secure, contains less bloat which improves performance, and has no block editor (Gutenberg).

Coding Standards PHPUnit Tests JavaScript Tests PHP Compatibility

For more information, see:

Contributions

This project exists thanks to all the people who contribute and who have contributed in the past, whether as part of the long history of thousands of contributions to WordPress from many different people, or as contributions to ClassicPress itself.

Would you like to help? Here is how you can start.

We are working on several ways to recognize people for their contributions to ClassicPress. In the meantime, you can view a list of code contributions here on GitHub.

Donate to support ClassicPress

Support the ClassicPress project by making a donation! 🙏
All donations are tax-deductible in the United States.

Comments
  • Renovate[bot]: Update dependency grunt-contrib-qunit to v6.2.0

    Renovate[bot]: Update dependency grunt-contrib-qunit to v6.2.0

    Mend Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | grunt-contrib-qunit | 6.0.0 -> 6.2.0 | age | adoption | passing | confidence |


    Release Notes

    gruntjs/grunt-contrib-qunit

    v6.2.0

    Compare Source

    • Enable --no-sandbox by default for CI environments. 0db7a35
    • Add support for CHROMIUM_FLAGS environment variable. 0db7a35

    v6.1.0

    Compare Source

    • Migrate reporting logic to QUnit.on() events API db80b86
    • Add docs for qunit.on.* events, and fix various links 72a71b0

    Configuration

    📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by Mend Renovate. View repository job log here.

    help wanted type: bot status: on hold 
    opened by renovate[bot] 142
  • Redesign of installation screens for improved identity and branding

    Redesign of installation screens for improved identity and branding

    The installation screens have gotten zero love over the years and their current state is excessively verbose (item 5?... that's fully described in 2 places!) Specifically, I'd love to see several changes; quick mockup below.

    1. full-size CP wordmark + feather logo at the top (round logo for mobile/responsive views)
    2. installation button styled as a CTA with CP colors and proper labeling
    3. succinct texts, with links to anything requiring description or more information
    4. larger text (ie, 115%)

    Expected behavior

    The install screens do already behave as expected.

    Current behavior

    Install screens are overly verbose and there's little distinction between CP and WP.

    Possible solution

    Mild redesign of the colors/texts and how they are laid out.

    Steps to reproduce (for bugs)

    Install ClassicPress.

    Context

    I've always felt these screens were overlooked. This is a great place to insert CP colors and make an immediate distinction between the CP/WP platforms.

    image

    type: feature request status: has pr 
    opened by johnalarcon 45
  • Renovate[bot]: Update dependency @rollup/plugin-commonjs to v23

    Renovate[bot]: Update dependency @rollup/plugin-commonjs to v23

    Mend Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | @rollup/plugin-commonjs (source) | 22.0.2 -> 23.0.0 | age | adoption | passing | confidence |


    Release Notes

    rollup/plugins

    v23.0.0

    Compare Source

    2022-10-09

    Breaking Changes

    Configuration

    📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by Mend Renovate. View repository job log here.

    bot 
    opened by renovate[bot] 43
  • Renovate[bot]: Update dependency rollup to v2.45.2

    Renovate[bot]: Update dependency rollup to v2.45.2

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | rollup (source) | 2.26.11 -> 2.45.2 | age | adoption | passing | confidence |


    Release Notes

    rollup/rollup

    v2.45.2

    Compare Source

    2021-04-13

    Bug Fixes
    • Do not user a dynamic entry file name for naming a manual chunk (#​4040)
    Pull Requests

    v2.45.1

    Compare Source

    2021-04-10

    Bug Fixes
    • Handle falsy return values from async plugin options hooks (#​4039)
    Pull Requests

    v2.45.0

    Compare Source

    2021-04-09

    Features
    • Support private class instance methods and accessors (#​4034)
    Pull Requests

    v2.44.0

    Compare Source

    2021-03-29

    Features
    • Add a new option makeAbsoluteExternalsRelative to opt out of renormalizing absolute external ids to relative ids (#​4021)
    • Extend the resolveId plugin hook to allow forcing or preventing renormalization of absolute external ids (#​4021)
    • Make the rendered code of individual modules available in the generated bundle (#​4028)
    Bug Fixes
    • Handle objects with __proto__ properties correctly (#​4019)
    Pull Requests

    v2.43.1

    Compare Source

    2021-03-28

    Bug Fixes
    • Prevent infinite recursions in certain scenarios when calling object properties (#​4025)
    Pull Requests

    v2.43.0

    Compare Source

    2021-03-27

    Features
    • Track side effects of function properties in objects for better tree-shaking (#​4011)
    Pull Requests

    v2.42.4

    Compare Source

    2021-03-24

    Bug Fixes
    • Do not discard plugin return values when using perf option (#​4010)
    Pull Requests

    v2.42.3

    Compare Source

    2021-03-22

    Bug Fixes
    • Do not ignore #__PURE__ comments in front of optional chaining expressions (#​4007)
    Pull Requests

    v2.42.2

    Compare Source

    2021-03-22

    Bug Fixes
    • Use correct import.meta.url in relative imports from transpiled config files (#​4005)
    Pull Requests

    v2.42.1

    Compare Source

    2021-03-20

    Bug Fixes
    • Do not produce unhandled Promise rejections when plugins throw while using the perf option (#​4004)
    Pull Requests

    v2.42.0

    Compare Source

    2021-03-19

    Features
    • Prevent infinite loops when several plugins are using this.resolve in their resolveId hook (#​4000)
    Pull Requests

    v2.41.5

    Compare Source

    2021-03-18

    Bug Fixes
    • Make sure unused property accesses of external namespaces can be tree-shaken (#​4001)
    Pull Requests

    v2.41.4

    Compare Source

    2021-03-16

    Bug Fixes
    • Do not replace external namespace imports with individual named imports to avoid changing behaviour with regard to missing exports (#​3999)
    Pull Requests

    v2.41.3

    Compare Source

    2021-03-16

    Bug Fixes
    • Always retain arguments passed to empty object pattern parameters (#​3998)
    Pull Requests

    v2.41.2

    Compare Source

    2021-03-12

    Bug Fixes
    • Also remove sourcemaps comments if plugins return a pre-made ast (#​3987)
    Pull Requests

    v2.41.1

    Compare Source

    2021-03-11

    Pull Requests

    v2.41.0

    Compare Source

    2021-03-09

    Features
    • Add option to treeshake.propertyReadSideEffects to keep all property accesses (#​3985)
    Bug Fixes
    • Also respect pure comment annotations when a plugin provides an AST in the transform hook provided they use this.parse (#​3981)
    Pull Requests
    • #​3981: Move pure comment annotation to Graph.contextParse (@​yannayl)
    • #​3985: implement --treeshake.propertyReadSideEffects=always to handle getters with side effects (@​kzc)

    v2.40.0

    Compare Source

    2021-02-26

    Features
    • Make sure that entry point variable names take precedence over variable names in dependencies when deconflicting (#​3977)
    Bug Fixes
    • Replace : in generated file names to prevent invalid files on Windows (#​3972)
    Pull Requests

    v2.39.1

    Compare Source

    2021-02-23

    Bug Fixes
    • Make sure local variables named Symbol, Object or Promise do not conflict with code generated by Rollup (#​3971)
    Pull Requests

    v2.39.0

    Compare Source

    2021-02-12

    Features
    • Add "validate" option to verify generated chunks are valid JavaScript (#​3952)
    Bug Fixes
    • Always add exports properties for uninitialized named exports (#​3957)
    • Allow using an external namespace reexport together with named exports (#​3959)
    • Avoid invalid generated code in certain scenarios with SystemJS exports (#​3960)
    Pull Requests

    v2.38.5

    Compare Source

    2021-02-05

    Bug Fixes
    • Prevent invalid code when simplifying assignments and delcarations (#​3951)
    • Prevent behaviour-changing line-breaks when simplifying assignments in return statements (#​3951)
    • Slightly improve white-space rendering when simplifying certain expressions (#​3951)
    Pull Requests

    v2.38.4

    Compare Source

    2021-02-02

    Bug Fixes
    • Do not change logic when tree-shaking declarations in if statements or loops (#​3947)
    Pull Requests

    v2.38.3

    Compare Source

    2021-02-01

    Bug Fixes
    • Prevent an unexpected live-binding when default exporting a synthetic named export (#​3946)
    Pull Requests

    v2.38.2

    Compare Source

    2021-01-31

    Bug Fixes
    • Do not generate invalid code for partially tree-shaken declarations in for loops (#​3943)
    • Always include function bodies of functions in side-effect-free modules (#​3944)
    Pull Requests

    v2.38.1

    Compare Source

    2021-01-28

    Bug Fixes
    • Fix internal error when resolving a missing entry point in the browser build (#​3935)
    Pull Requests

    v2.38.0

    Compare Source

    2021-01-22

    Features
    • Entirely remove declared variables that only have an initializer side effect (#​3933)
    Pull Requests

    v2.37.1

    Compare Source

    2021-01-20

    Pull Requests

    v2.37.0

    Compare Source

    2021-01-19

    Features
    • Always check modules for side effects that only indirectly reexport a used variable (#​3840)
    • Warn if a circular dependency would cause wrong execution order when preserving modules (#​3840)
    Bug Fixes
    • Allow consuming synthetic exports via modules that reexport a namespace (#​3894)
    • Do not crash for circular default reexports (#​3840)
    • Do not crash for circular synthetic namespaces (#​3840)
    • Improve circular dependency execution order in certain scenarios (#​3840)
    Pull Requests

    v2.36.2

    Compare Source

    2021-01-16

    Bug Fixes
    • Fix an issue where invalid code was generated for unused assignments with side effects (#​3926)
    Pull Requests

    v2.36.1

    Compare Source

    2021-01-06

    Bug Fixes
    • Solve issues that result in invalid code when partially removing assignments (#​3921)
    Pull Requests

    v2.36.0

    Compare Source

    2021-01-05

    Features
    • Support partial tree-shaking of chained assignments and unused assignment targets (#​3919)
    Pull Requests

    v2.35.1

    Compare Source

    2020-12-14

    Bug Fixes
    • Allow closing the bundle when watching in case of generate errors by adding the bundle to the error event (#​3909)
    • Automatically close all bundles on generate errors when watching and using the CLI (#​3909)
    • Try to create remaining bundles when watching and one of them throws (#​3909)
    Pull Requests

    v2.35.0

    Compare Source

    2020-12-14

    Features
    • Add closeBundle hook that is triggered by bundle.close() in the JS API (#​3883)
    Pull Requests

    v2.34.2

    Compare Source

    2020-12-06

    Bug Fixes
    • Revert pattern export change (#​3898)
    Pull Requests

    v2.34.1

    Compare Source

    2020-12-03

    Bug Fixes
    • Avoid Node deprecation warning by using a pattern export for nested Rollup files (#​3896)
    Pull Requests

    v2.34.0

    Compare Source

    2020-11-29

    Features
    • Support RequireJS comaptible AMD ids in code-splitting builds via amd.autoId (#​3867)
    • Allow adding an AMD id base path (#​3867)
    Bug Fixes
    • Warn when using an constant AMD id in a code-splitting build (#​3867)
    Pull Requests

    v2.33.3

    Compare Source

    2020-11-18

    Bug Fixes
    • Do not use .js extension when importing AMD files from a UMD bundle (#​3872)
    Pull Requests

    v2.33.2

    Compare Source

    2020-11-14

    Bug Fixes
    • Fix an issue where statements were ignored after a conditional return in a labeled statement (#​3871)
    Pull Requests

    v2.33.1

    Compare Source

    2020-11-02

    Bug Fixes
    • Add syntheticNamedExports to this.getModuleInfo to align with documentation (#​3847)
    Pull Requests

    v2.33.0

    Compare Source

    2020-11-01

    Features
    • Add parameter to "watchChange" hook to denote if a change was an addition, update or deletion (#​3841)
    • Add "closeWatcher" hook to allow plugins to clean up resources when the watcher is closed (#​3841)
    • Add "this.getWatchFiles" function to plugin context to get the current set of watched files (#​3841)
    Pull Requests

    v2.32.1

    Compare Source

    2020-10-21

    Bug Fixes
    • Print warning location for plugin warnings if only loc is supplied (#​3824)
    Pull Requests

    v2.32.0

    Compare Source

    2020-10-16

    Features
    • Extend preserveEntrySignatures with a value "exports-only" to allow extension only if an entry does not have exports (#​3823)
    Pull Requests

    v2.31.0

    Compare Source

    2020-10-15

    Features
    • When using the output.moduleToStringTag option, also add the tag to entries with exports and simulated external namespaces (#​3822)
    • Add the __esModule interop marker to IIFE global variables unless output.esModule is turned off (#​3822)
    Pull Requests

    v2.30.0

    Compare Source

    2020-10-13

    Features
    • Add moduleParsed hook that is called for each module once code and AST are available (#​3813)
    • Include code and AST in this.getModuleInfo (#​3813)
    Bug Fixes
    • Provide the original Acorn AST instead of the internal one when resolving dynamic imports that contain non-trivial expressions (#​3813)
    Pull Requests

    v2.29.0

    Compare Source

    2020-10-08

    Features
    • Allow passing custom options to other plugins via this.resolve (#​3807)
    • Allow attaching custom meta information to modules when resolving, loading or transforming (#​3807)
    • Do not throw but return null when using this.getModuleInfo for an unknown id (#​3807)
    Bug Fixes
    • Trigger build in watch mode when files are added to a watched directory (#​3812)
    • Make code optional when transforming modules (#​3807)
    Pull Requests

    v2.28.2

    Compare Source

    2020-09-24

    Bug Fixes
    • Fix a source of possible variable name conflicts when using preserveModules with SystemJS (#​3796)
    Pull Requests

    v2.28.1

    Compare Source

    2020-09-21

    Bug Fixes
    • Fix a path slash issue when using the preserveModulesRoot option on Windows (#​3791)
    Pull Requests

    v2.28.0

    Compare Source

    2020-09-21

    Features
    • Add an option to treat modules at a given path as located at root when preserving modules (#​3786)
    Pull Requests

    v2.27.1

    Compare Source

    2020-09-17

    Bug Fixes
    • Do not fail when using ES module imports in symlinked config files (#​3783)
    Pull Requests

    v2.27.0

    Compare Source

    2020-09-16

    Features
    • Support specifying a file extension when reading from stdin (#​3775)
    Bug Fixes
    • Do not break logic if a branch with hoisted variables is tree-shaken in an else-if statement (#​3782)
    Pull Requests

    Configuration

    :date: Schedule: At any time (no schedule defined).

    :vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

    :recycle: Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

    :no_bell: Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, check this box.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    type: bot 
    opened by renovate[bot] 43
  • Renovate[bot]: Update dependency rollup to v2.60.1

    Renovate[bot]: Update dependency rollup to v2.60.1

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | rollup (source) | 2.47.0 -> 2.60.1 | age | adoption | passing | confidence |


    Release Notes

    rollup/rollup

    v2.60.1

    Compare Source

    2021-11-22

    Bug Fixes
    • Make sure virtual files have proper file extensions when preserving modules (#​4270)
    Pull Requests

    v2.60.0

    Compare Source

    2021-11-11

    Features
    • Add this.load context function to load, transform and parse modules without adding them to the graph (#​4234)
    • Sanitize non-url-safe characters in generated chunk names by default (#​4262)
    • Support ESM plugins via command line (#​4265)
    Pull Requests

    v2.59.0

    Compare Source

    2021-11-01

    Features
    • Support static class initialization blocks (#​4249)
    Bug Fixes
    • Fix an issue with the CommonJS plugin when module.exports has inherited properties (#​4256)
    Pull Requests

    v2.58.3

    Compare Source

    2021-10-25

    Bug Fixes
    • Republish 2.58.1 with npm 6 as files were missing

    v2.58.2

    Compare Source

    2021-10-25

    Bug Fixes
    • Republish 2.58.1 as files were missing

    v2.58.1

    Compare Source

    2021-10-25

    Bug Fixes
    • Fix an issue with the CommonJS plugin when module.exports is falsy (#​4247)
    Pull Requests

    v2.58.0

    Compare Source

    2021-10-01

    Features
    • Add a flag to more reliably identify entry points in the resolveId hook (#​4230)
    Pull Requests

    v2.57.0

    Compare Source

    2021-09-22

    Features
    • Add generatedCode option to allow Rollup to use es2015 features for smaller output and more efficient helpers (#​4215)
    • Improve AMD and SystemJS parsing performance by wrapping relevant functions in parentheses (#​4215)
    • Using preferConst will now show a warning with strictDeprecations: true (#​4215)
    Bug Fixes
    • Improve ES3 syntax compatibility by more consequently quoting reserved words as props in generated code (#​4215)
    • Do not use Object.assign in generated code to ensure ES5 compatibility without the need for polyfills (#​4215)
    • Support live-bindings in dynamic namespace objects that contain reexported external or synthetic namespaces (#​4215)
    • Use correct "this" binding in dynamic import expressions for CommonJS and AMD (#​4215)
    • Properly handle shimMissingExports for exports that are only used internally (#​4215)
    • Prevent unhandled rejection for failed module parsing (#​4228)
    Pull Requests

    v2.56.3

    Compare Source

    2021-08-23

    Bug Fixes
    • Make sure moduleInfo contains complete information about imported ids in the moduleParsed hook (#​4208)
    Pull Requests

    v2.56.2

    Compare Source

    2021-08-10

    Bug Fixes
    • Check if after simplification, an object pattern would become an expression statement or arrow function return value (#​4204)
    Pull Requests

    v2.56.1

    Compare Source

    2021-08-08

    Bug Fixes
    • Fix rendering of SystemJS export declarations initialized with a simplifiable expression (#​4202)
    Pull Requests

    v2.56.0

    Compare Source

    2021-08-05

    Features
    • Create more efficient code for SystemJS exports (#​4199)
    • Extend maxParallelFileReads option to also throttle plugin load hooks (#​4200)
    Bug Fixes
    • Return correct value for postfix update expressions of exported variables (#​4194)
    Pull Requests

    v2.55.1

    Compare Source

    2021-07-29

    Bug Fixes
    • Improve CLI warning message for unused external imports (#​4194)
    Pull Requests

    v2.55.0

    Compare Source

    2021-07-28

    Features
    • Support default export live-bindings when generating ESM output (#​4182)
    Bug Fixes
    • Always write ["default"] as computed property when used as named export (#​4182)
    • Do not mask default export TDZ errors (#​4182)
    Pull Requests

    v2.54.0

    Compare Source

    2021-07-25

    Features
    • Extend UMD import.meta.url polyfill to support web workers (#​4186)
    Bug Fixes
    • Resolve an issue where certain uses of classes could lead to an infinite recursion (#​4189)
    Pull Requests

    v2.53.3

    Compare Source

    2021-07-21

    Bug Fixes
    • Solve an issue that could lead to severe memory issues and crashes when there are a lot of hoisted variables (#​4183)
    Pull Requests

    v2.53.2

    Compare Source

    2021-07-15

    Bug Fixes
    • Identify additional TDZ situations in functions that are run more than once (#​4177)
    • Fix a scoping issue when a variable inside a catch scope matches the scope parameter's name (#​4178)
    Pull Requests

    v2.53.1

    Compare Source

    2021-07-11

    Bug Fixes
    • Do not omit namespace reexports when treeshake is false (#​4175)
    Pull Requests

    v2.53.0

    Compare Source

    2021-07-09

    Features
    • Add maxParallelFileReads option to limit read operations with a default of 20 (#​4170)
    Pull Requests

    v2.52.8

    Compare Source

    2021-07-07

    Bug Fixes
    • Automatically handle many use var before declaration and TDZ access scenarios correctly without the need for treeshake.correctVarValueBeforeDeclaration (#​4148)
    Pull Requests

    v2.52.7

    Compare Source

    2021-07-02

    Bug Fixes
    • Fix an issue where reassignments where not tracked through async function returns (#​4163)
    Pull Requests

    v2.52.6

    Compare Source

    2021-07-01

    Bug Fixes
    • Fix an issue where reassignments where not tracked through an await expression (#​4162)
    Pull Requests

    v2.52.5

    Compare Source

    2021-07-01

    Bug Fixes
    • Properly display parser errors not tied to a code location (#​4160)
    Pull Requests

    v2.52.4

    Compare Source

    2021-06-30

    Bug Fixes
    • Fix an error when external namespaces are reexported across several files (#​4159)
    Pull Requests

    v2.52.3

    Compare Source

    2021-06-25

    Bug Fixes
    • Fix an issue where code was wrongly removed when using vars in nested scopes (#​4149)
    Pull Requests

    v2.52.2

    Compare Source

    2021-06-21

    Bug Fixes
    • Support falsy plugins in types (#​4144)
    • Do not require return value in renderChunkHook type (#​4144)
    Pull Requests

    v2.52.1

    Compare Source

    2021-06-17

    Bug Fixes
    • Fix a memory leak in watch mode (#​4142)
    Pull Requests

    v2.52.0

    Compare Source

    2021-06-16

    Features
    • Add --configPlugin CLI option to apply plugins to the config file for e.g. TypeScript configs (#​3835)
    • Add "safest" and "smallest" presets to tree-shaking options for easier configuration (#​4131)
    • Add treeshake.correctVarValueBeforeDeclaration option to deoptimize var declarations (#​4139)
    Pull Requests

    v2.51.2

    Compare Source

    2021-06-11

    Bug Fixes
    • Include modules imported from no-treeshake modules even if they would be empty (#​4138)
    Pull Requests

    v2.51.1

    Compare Source

    2021-06-08

    Bug Fixes
    • Fix error when using defineConfig (#​4134)
    Pull Requests

    v2.51.0

    Compare Source

    2021-06-06

    Features
    • Add a helper for IntelliSense support in config files (#​4127)
    Bug Fixes
    • Improve performance when generating source maps (#​4122)
    Pull Requests

    v2.50.6

    Compare Source

    2021-06-03

    Bug Fixes
    • Do not consider the object spread operator as side effect when propertyReadSideEffects are false (#​4119)
    • Detect side effects when returning thenables from async arrow functions (#​4120)
    Pull Requests

    v2.50.5

    Compare Source

    2021-05-30

    Bug Fixes
    • Detect side effects when accessing thenables (#​4115)
    Pull Requests

    v2.50.4

    Compare Source

    2021-05-29

    Bug Fixes
    • Fix a situation where tree-shaking would stop including nodes prematurely (#​4111)
    • Track mutations and accessor side effects when using __proto__ in an object literal (#​4112)
    • Check for getter effects when spreading an object (#​4113)
    Pull Requests

    v2.50.3

    Compare Source

    2021-05-28

    Bug Fixes
    • Wrap parentheses around leading elements in simplified sequence expressions if this would otherwise lead to invalid code (#​4110)
    • Do not associate block soped variables in catch clauses with the clause parameter (#​4108)
    • Do not associate hoisted variables in catch clauses with outside variables if they match the parameter (#​4108)
    • Use correct "this" context for tagged template literal member expressions in simplified sequences (#​4110)
    Pull Requests

    v2.50.2

    Compare Source

    2021-05-27

    Bug Fixes
    • Avoid unnecessary side effects when using methods like .filter and .map (#​4103)
    • Avoid crash when a module with moduleSideEffects no-treeshake imports a tree-shaken module (#​4104)
    Pull Requests

    v2.50.1

    Compare Source

    2021-05-26

    Bug Fixes
    • Do not associate pure annotations in simplified expressions with wrong elements (#​4095)
    • Prevent invalid code when simplified conditionals start with an IIFE function expression (#​4099)
    Pull Requests

    v2.50.0

    Compare Source

    2021-05-25

    Features
    • Only include last elements of comma expressions if they are used or have side effects (#​4087)
    Bug Fixes
    • Prevent a crash that could occur when calling object methods (#​4091)
    Pull Requests

    v2.49.0

    Compare Source

    2021-05-23

    Features
    • Detect side-effect-free static class methods and properties (#​4018)
    • Detect side-effect-free array elements (#​4018)
    • Do not apply deoptimizations from dead code (#​4018)
    Bug Fixes
    • Handle side effect detection for getters and setters added in untracked code (#​4018)
    • Track "this" mutations for methods, getters and setters (#​4018)
    Pull Requests

    v2.48.0

    Compare Source

    2021-05-15

    Features
    • Add replacement to conditionally insert asset extensions in entryFileNames when preserving modules (#​4077)
    Bug Fixes
    • Fix crash when dynamically assigning to namespace members (#​4070)
    • Do not associate pure annotations in front of a semi-colon or comma with succeeding code (#​4068)
    Pull Requests

    Configuration

    📅 Schedule: At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    type: bot 
    opened by renovate[bot] 41
  • What to do with plugin installation section

    What to do with plugin installation section

    As per this discussion on Slack and @nylen suggestion to make it an issue, I'm opening it as an issue so it doesn't get lost.

    Possibilities

    There are several possibilities brought up in the discussion

    • remove all, keep search
    • leave as is, but remove Gutenberg and related, and do the improvements in v2
    • remove featured tab and switch first tab to search box
    • NEW IDEA change current popular tab with latest plugins that have been added to the Plugins Directory and of course the Search tab may stay, rest removed

    More possible

    status: has pr 
    opened by senlin 41
  • Discussion: Collaboration between calmPress and ClassicPress

    Discussion: Collaboration between calmPress and ClassicPress

    @markkap, the creator of calmPress has done an incredible job with his project and most of the changes he has applied to it could be of important use for ClassicPress as well.

    My suggestion would be the following: we need to set up a common ground that could benefit not only these two projects, but also any other person or company is interested in forking WordPress for their own preferences and interests.

    Think of this as a form of a lightweight fooPress framework that could play the role of a headless core that anyone could build on top of it, without deviating from its original schema.

    Please bear in mind that this suggestion is for future versions of both projects, after they become solid, stable, and robust.

    status: discussion scope: community 
    opened by stefanos82 39
  • Replace WordPress events in dashboard with feature votes

    Replace WordPress events in dashboard with feature votes

    Let's decide what to do about the WordPress events feed that comes through in the admin dashboard.

    I think we should remove it from ClassicPress, because these are officially sponsored WordPress events, and it doesn't seem fair to encourage people to "crash the party" so to speak.

    This will also eliminate some calls to the WordPress.org APIs.

    status: has pr 
    opened by nylen 35
  • Add new theme_support type: body-only

    Add new theme_support type: body-only

    This is to implement the petition for core to have more control over the front end.

    Motivation and context

    The two main goals are

    • the required calls like wp_head(), wp_footer(), wp_body_open() are handled by core, not the theme
    • core provides a standardized way to filter attributes on the HTML

    The approach used is to add a new theme_support called 'body-only' with the intent that the theme is written to handle the HTML that goes in the body of the page, and expects core to do the rest (enqueuing scripts and styles is unaffected). The theme_support code calls for 'automatic-feed-links', 'title-tag', and 'html5'.

    The template loader checks for 'body-only' and calls two new functions do_html5_header and do_html5_footer. It's important that the include for the template file remains as-is, so that the scope of variables in the template file is not affected. To make the <head> section HTML flexible, the attributes are filtered using a new function cp_attributes. Themes would be able to use the same function to get a standardized way to filter HTML attributes. The existing filters are unaffected. Future enhancements can be made easily by using cp_attributes in core functions that generate HTML. (See https://github.com/ClassicPress/ClassicPress/pull/792#issuecomment-985174415)

    For themes: There's no enforcement of using the cp_attributes function, but it would be expected if calling add_theme_support('body-only'). The changes needed for a 'body-only' theme:

    • in functions.php, call add_theme_support('body-only')
      • remove add_theme_support for 'title-tag', 'html5', 'automatic-feed-links'
    • in header.php, remove all HTML output before and including the <body> tag
      • remove output of pingback_url
    • in footer.php, remove wp_footer(), </body>, and </html>
    • to modify the viewport meta, use 'cp_attributes' filter

    How has this been tested?

    PR includes tests for new cp_attributes function. I made minor changes to a copy of Twenty Fifteen and ran it locally to test the other changes.

    Types of changes

    New feature

    task: needs 2nd review 
    opened by joyously 31
  • Will the fork also address other issues?

    Will the fork also address other issues?

    Will this fork also address issues like below or will it "just" be WP 4.9.8 without Gutenberg?

    • remove the Customizer
    • remove REST API
    • remove XML-RPC
    • remove all pre-PHP 7 support
    • remove hardcoded jQuery
    • remove oEmbeds, emojis and all useless content filters
    • remove old code, old functions, deprecated function support

    (part of the list copied from a comment on WP Tavern)

    status: discussion 
    opened by senlin 29
  • Remove dns-prefetch and assets loaded from s.w.org

    Remove dns-prefetch and assets loaded from s.w.org

    I have found two places that mention dns-prefetch that points at s.w.org which redirects to WordPress's website.

    Also, it can be found in ClassicPress's website as <link rel='dns-prefetch' href='//s.w.org' />.

    Is there a particular reason we need it?

    Please advise.

    Thank you.

    help wanted status: has pr 
    opened by stefanos82 28
  • 💡 Automate changelog and release notes generation

    💡 Automate changelog and release notes generation

    Context

    Creating changelogs and release notes can be a pain in the butt. We can eliminate this headache by automating the process.

    Possible Solution

    Generating changelog and release notes automatically can easily be done using a tool such as: https://github.com/googleapis/release-please

    But in order to use it all committers would need to follow Conventional Commits when writing their commit messages: https://www.conventionalcommits.org/en/v1.0.0/

    This also ties in with our use of SemVer.

    The one thing I'm not sure about is commits from WordPress. Non-conforming commits are supposed to be thrown out if I read correctly.

    The other thing to consider, would this work with our release process?

    Will you be able to help with the implementation?

    I will use Conventional Commits to write commit messages.

    type: feature request status: discussion 
    opened by viktorix 0
  • External HTTP test failures 📋

    External HTTP test failures 📋

    WordPress trac tickets

    https://core.trac.wordpress.org/ticket/57306

    WordPress changesets

    https://core.trac.wordpress.org/changeset/54955

    Context

    Upstream reports details failure on external HTTP tests.

    Our tests are encountering the same issue.

    We should investigate this backport to see if it helps restore passing tests again and keep monitoring the original ticket for a more permanent fix.

    Can you help?

    Yes, I will submit a PR

    good first issue status: needs triage type: wp backport 
    opened by mattyrob 0
  • 📋 Use feature image of video attachment as preview instead of icon

    📋 Use feature image of video attachment as preview instead of icon

    WordPress trac tickets

    https://core.trac.wordpress.org/ticket/49852

    WordPress changesets

    https://core.trac.wordpress.org/changeset/54941

    Context

    Media: Use featured image if available for attachment as preview instead of icon.

    When rendering a list of attachments in WP_Media_List_Table class, none image attachments, show a generic icon. However, attachment types like audio and video support adding a featured image. For attachments that have featured images, us this image instead of the icon. This featured image is a better preview than a generic icon.

    Can you help?

    Yes, I will submit a PR

    good first issue type: wp backport 
    opened by bahiirwa 0
  • Update PHPMailer to 6.7.0 📋

    Update PHPMailer to 6.7.0 📋

    WordPress trac tickets

    https://core.trac.wordpress.org/ticket/57281

    WordPress changesets

    https://core.trac.wordpress.org/changeset/54937

    Context

    No response

    Can you help?

    Yes, I will submit a PR

    flag: build change type: wp backport 
    opened by bahiirwa 0
  • Customizer: Fetch presence of published pages more optimally🐞

    Customizer: Fetch presence of published pages more optimally🐞

    Expected behavior

    Ref: https://core.trac.wordpress.org/ticket/55425

    The has_published_pages() seems to fetch all the data of pages, whereas what is needed is only whether published pages exist or not.

    Current behavior

    While this may not matter much in sites that have fewer pages, on website that has too many pages, it may create an out of memory error. I will test and submit a patch to fetch only the count of published pages that will help improve efficiency.

    Possible solution

    Backports https://core.trac.wordpress.org/changeset/53057 https://core.trac.wordpress.org/changeset/54935

    Steps to reproduce bug

    Check has_published_pages() in the codebase.

    Context

    No response

    ClassicPress version

    1.4.4+dev

    PHP version

    8.0

    Can you help?

    Yes, I will submit a PR

    type: bug good first issue type: wp backport 
    opened by bahiirwa 0
  • adding calls to cp_attributes for front end HTML

    adding calls to cp_attributes for front end HTML

    This is a work-in-progress, to add usage of the new core function cp_attributes to HTML that is output on the front end of a site. The goal is to give themes and plugins more ways to tweak the core output. The HTML for the admin pages is to be handled separately.

    How has this been tested?

    I have done local testing of manual inspection of the HTML in front end pages. One way to test is to save the generated pages from a site(plugin), checkout this PR and save the same pages, then compare them. They should be the same, except perhaps double quotes instead of single quotes in some places. For coverage, I have used a small test filter that adds a title attribute containing the HTML tag and context. Inspecting the HTML to see if all tags have a title attribute will expose tags that were missed.

    Types of changes

    New feature -- output HTML with the attributes filterable

    opened by joyously 3
Releases(1.5.0+dev)
Azuriom - a modern, reliable, fast and secure game CMS.

Azuriom is the next generation game CMS, it's free and open-source, and is a modern, reliable, fast and secure alternative to existing CMS so you can have the best web experience possible.

Azuriom 281 May 5, 2022
Flextype is an open-source Hybrid Content Management System with the freedom of a headless CMS and with the full functionality of a traditional CMS

Flextype is an open-source Hybrid Content Management System with the freedom of a headless CMS and with the full functionality of a traditional CMS. Building this Content Management System, we focused on simplicity. To achieve this, we implemented a simple but powerful API's.

Flextype 524 Dec 30, 2022
PHPVibe Open source video CMS / Video Sharing CMS / Youtube Api v3 / Video Embeds

PHPVibe Video CMS Free Video Sharing CMS The modern choice of design inspired by Youtube and a social videos sharing module that may just cut it for y

MediaVibe 71 Dec 18, 2022
NukeViet 132 Nov 27, 2022
BaiCloud-cms is a powerful open source CMS that allows you to create professional websites and scalable web applications. Visit the project website for more information.

BaiCloud-cms About BaiCloud-cms is a powerful open source CMS that allows you to create professional websites and scalable web applications. Visit the

null 5 Aug 15, 2022
Baicloud CMS is a lightweight content management system (CMS) based on PHP and MySQL and running on Linux, windows and other platforms

BaiCloud-cms About BaiCloud-cms is a powerful open source CMS that allows you to create professional websites and scalable web applications. Visit the

null 5 Aug 15, 2022
Doptor CMS is a Laravel 5 based CMS

Introduction Doptor CMS is a Laravel 5 based CMS. Find out more about Doptor by reading below. ;) About Doptor CMS Doptor is an Integrated and well-de

DOPTOR 4 Sep 11, 2022
Bismuth CMS is a ready-made Website CMS based on Yii 2 Advance Template

Bismuth CMS is a ready-made Website CMS based on Yii 2 Advance Template, it's the simplest and easy to set up CMS you may come across.

Hamadas Telebrain 1 Feb 11, 2022
Bootstrap CMS - PHP CMS powered by Laravel 5 and Sentry

Bootstrap CMS Bootstrap CMS was created by, and is maintained by Graham Campbell, and is a PHP CMS powered by Laravel 5.1 and Sentry. It utilises many

Bootstrap CMS 2.5k Dec 27, 2022
GetSimple CMS - a flatfile CMS that works fast and efficient and has the best UI around, it is written in PHP

GetSimple CMS is a flatfile CMS that works fast and efficient and has the best UI around, it is written in PHP.

null 370 Dec 30, 2022
Amila Laravel CMS - Free, open-source Simple Bootstrap Laravel CMS

Simple Bootstrap Laravel CMS. Support Laravel 8.x Can integrate into any existing Laravel project. Only add few database tables with prefixes, not affect your existing database tables. Support Laravel 7.x & Laravel 6.x & Laravel 5.x & MySql & PostgreSql - Amila Laravel CMS

Alex Zeng 96 Sep 6, 2022
ExpressionEngine is a mature, flexible, secure, free open-source content management system.

ExpressionEngine is a flexible, feature-rich, free open-source content management platform that empowers hundreds of thousands of individuals and organizations around the world to easily manage their web site.

ExpressionEngine 366 Mar 29, 2022
Modern, Crazy Fast, Ridiculously Easy and Amazingly Powerful Flat-File CMS

Grav Grav is a Fast, Simple, and Flexible, file-based Web-platform. There is Zero installation required. Just extract the ZIP archive, and you are alr

Grav 13.6k Jan 4, 2023
Self-hosted CMS platform based on the Laravel PHP Framework.

October is a Content Management System (CMS) and web platform whose sole purpose is to make your development workflow simple again. It was born out of

October CMS 10.8k Jan 4, 2023
Craft is a flexible, user-friendly CMS for creating custom digital experiences on the web and beyond.

About Craft CMS Craft is a flexible, user-friendly CMS for creating custom digital experiences on the web and beyond. It features: An intuitive, user-

Craft CMS 2.9k Jan 1, 2023
Pyro is an experienced and powerful Laravel PHP CMS.

PyroCMS PyroCMS is an easy to use, powerful, and modular CMS and development platform built with Laravel 5. Security If you discover any security rela

PyroCMS 3.1k Dec 23, 2022
Multilingual PHP CMS built with Laravel and bootstrap

Lavalite This is an open source of Content Management System developed with Laravel framework. Documentation Visit Documentation section in the websit

LavaLite 2.6k Jan 4, 2023
Multilingual CMS built with Laravel.

TypiCMS TypiCMS is a modular multilingual content management system built with Laravel. Out of the box you can manage pages, events, news, places, men

TypiCMS, Laravel multilingual CMS 1.1k Jan 7, 2023
Drag and Drop Website Builder and CMS with E-commerce

Microweber: Drag-and-Drop CMS Current version: 1.2 running on Laravel 8! Download | What is Microweber? | Core features of Microweber | Requirements |

Microweber 2.6k Dec 31, 2022