Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

wp-content symlink

Open
#26 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, php, wordpress

Research direction

Start by reading the repository's Elastic Beanstalk and EFS configuration instructions, focusing on wp-content and the /var/app/current/wp-content mount path. The issue does not name a configuration file or test; done would require a documented, supported approach for mounting EFS directly without symlink-resolved URLs breaking WordPress plugins and themes.

Written by the indexing model from the issue text.

Description

Hi,

I’m having hard time on adding persistence on all wp-content directory.

My main problem is that if I use symlink on wp-content, a lot of plugins/themes stop working because they use some FILE and DIR constants, and those constants return the real path of the file(the resolved path, so /wpfiles, where the EFS volume is mounted)

The result is all scripts/css have urls like : /wpfiles/themes/...

So I search for a way to mount directly the EFS on /var/app/current/wp-content, someone have some advices ?

Dominant language
PHP
Stars
166
Forks
92
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/eb-php-wordpress

All issues in aws-samples/eb-php-wordpress

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.