Download the PHP package wirefront/wplitecore without Composer

On this page you can find all versions of the php package wirefront/wplitecore. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of wirefront/wplitecore

Informations about the package wplitecore

WPLiteCore

A modern PHP framework for WordPress REST API interactions with both procedural and object-oriented programming approaches.

📍 Quick Navigation

👤 I want to USE WPLiteCore in my project:

👨‍💻 I want to CONTRIBUTE to WPLiteCore:

🚀 Quick Start for End Users

If you're using WPLiteCore in your project, it's very simple:

Installation

Basic Usage

🔓 JWT Authentication is Optional!

WPLiteCore automatically handles authentication based on whether you provide a secret key or not.

Procedural Functions (Backward Compatibility)

That's it! No configuration files, no setup scripts needed for end users.

🚀 High-Performance Caching System

WPLiteCore includes a powerful, multi-layered caching system that can dramatically improve your application's performance:

⚡ Performance Benefits

🔧 Cache System Components

  1. Core Cache System - File-based caching foundation
  2. API Response Caching - WordPress API call optimization
  3. Route Response Caching - Web route response optimization

📖 Complete Cache Documentation

Essential Cache Topics:

Quick Cache Example

Cache Management

🔗 Full Cache System Guide → - Complete documentation with examples, configuration, and best practices

🔧 For Library Developers and Contributors

⚠️ IMPORTANT: This section is for developers working ON the WPLiteCore library itself (contributors, maintainers, testers). If you're just USING WPLiteCore in your project, you can skip this entire section.

Development Environment Setup

If you're contributing to WPLiteCore or need to run tests:

1. Clone and Install

2. Development Configuration Setup

This creates a .env file for testing. You'll need to configure it with real API credentials for testing.

3. Manual Configuration (Alternative)

Edit the .env file:

Configuration System Details

Config.php Class

The Config.php class is used internally by library developers for:

Note for End Users: You don't need to use Config.php directly. Just pass your API details to WPLiteCore::create() as shown in the Quick Start section.

Developer Usage:

End User Usage (Simpler):

Environment Variables (For Library Developers Only)

End Users: You don't need to worry about environment variables. Just pass your API details directly to WPLiteCore::create().

For Library Testing and Development:

Variable Purpose Required for Tests Example
WPLITE_API_URL Test API endpoint ✅ Yes https://yoursite.com/wp-json/wp/v2
WPLITE_HASH_KEY Authentication key ✅ Yes your-secret-api-key
WPLITE_SITE_URL Test site URL ❌ Optional https://yoursite.com
WPLITE_TEST_POST_ID Post ID for testing ❌ Optional (default: 32) 123
WPLITE_TEST_MEDIA_ID Media ID for testing ❌ Optional (default: 41) 456
WPLITE_DEBUG Enable debug mode ❌ Optional (default: false) true

Why Environment Variables for Development?

What Happens Without Configuration

For End Users Using the Library: Nothing special - just pass your API details directly:

For Library Developers Running Tests: Tests will fail or be skipped without proper .env configuration:

Default fallbacks in development:

Configuration Summary

User Type Configuration Method Purpose Files Needed
End Users Direct parameters Using the library None - just use the library!
Library Developers .env file Testing & development .env (from .env.example)
CI/CD Systems Environment variables Automated testing Environment vars only

Running Tests

For comprehensive testing documentation, see 📋 Testing Guide

Quick Test Commands

Test Requirements

📖 Complete Testing Guide → - Detailed instructions, troubleshooting, and test descriptions

File Structure (Development)

Security for Developers

🔒 Critical Security Notes:

Testing Security:

Contributing

When contributing to WPLiteCore:

  1. Set up development environment using php setup.php
  2. Configure .env with your test API credentials
  3. Run tests to ensure nothing breaks: vendor/bin/phpunit
  4. Write tests for new features
  5. Update documentation if adding new functionality
  6. Never commit real API credentials or .env files

📚 API Reference

Core Classes

WPLiteCore

Main entry point for the library.

PostsClient

Handles WordPress posts operations.

ApiResponse

Handles API response data.

Legacy Functions

wlc_single_post()

Get a single post with all related data.

wlc_featured_image()

Get featured image for a specific attachment ID.

wlc_get_api_data()

Generic API data retrieval function.

🔄 Migration Guide

For detailed migration from procedural to OOP approach, see 📋 Migration Guide.

📖 Documentation & Examples

Document Description For
docs/USAGE.md Complete API reference with examples 👤 End Users
docs/COMPLETE_CACHE_SYSTEM.md Complete cache system guide 🚀 Performance
docs/CACHE_QUICK_START.md Cache quick start (5 minutes) ⚡ Quick Setup
docs/TESTING.md Testing guide and test descriptions 🔧 Contributors
docs/MIGRATION_GUIDE.md Upgrade from procedural to OOP 🔄 Existing Users
examples/simple_usage.php Simple usage examples 👤 End Users
examples/oop_usage_examples.php Advanced OOP examples 👤 End Users

🤝 Contributing

See the development setup section above. All contributions welcome!

📄 License

MIT License - see LICENSE file for details.

All versions of wplitecore with dependencies

PHP Build Version
Package Version
Requires php Version >=8.0
firebase/php-jwt Version ^6.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package wirefront/wplitecore contains the following files

Loading the files please wait ...