Still being developed, how to secure?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- php, wordpress
- Domain
- authorization, backend
Research direction
Start by reviewing the WordPress plugin's current handling of logged-in users and Node-RED device readings. Determine whether per-user data isolation is supported and document the security requirements or implementation scope needed to ensure users can access only their own readings.
Written by the indexing model from the issue text.
Description
Hi,
I'm looking to create a simple Wordpress site and expose some simple data to logged in users (their device readings from Node Red!). Can this be used to achieve this, how can I ensure that users can only see their device data?
Many thanks in advance for a superb plugin.
- Dominant language
- PHP
- Stars
- 20
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
phpstan/phpstan-doctrine#794 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Automattic/static-site-importer#1767 ·