josch87
Forum Replies Created
-
Hi @saranshwpm,
thank you for taking the time to test this.
I did some additional investigation and it seems the issue is related to the execution context of the Clipboard API.
The installation where the error occurs is running over HTTP, not HTTPS.
In that environment the following error appears in the console when clicking the Copy button:Uncaught TypeError: Cannot read properties of undefined (reading 'writeText')This suggests that
navigator.clipboardis not available in that context. As far as I understand, the Clipboard API is only available in secure contexts (HTTPS or localhost).I verified that
navigator.clipboardworks correctly in my browser in general, but in the affected WordPress installation it appears to be unavailable due to the HTTP context.This would explain why you are unable to reproduce the issue if your test environment is running over HTTPS.
It might be sufficient to add a simple guard before calling the Clipboard API:
if (navigator.clipboard && navigator.clipboard.writeText) {
// Modern Clipboard API (works in secure contexts like HTTPS)
navigator.clipboard.writeText(text);
} else {
// Clipboard API not available (e.g. HTTP context or older browsers)
// → optionally implement a fallback such as document.execCommand('copy')
// → or at least avoid the JavaScript error, hide the button, show the full link ...
}This would prevent the JavaScript error in environments where the Clipboard API is unavailable.
Hope this helps narrow it down.
Hi @saranshwpm,
thank you for testing this again.
Unfortunately your screencast did not show much. So I did some additional investigation and was able to narrow down when the issue occurs. It seems to be related to an upgrade scenario from older versions of BackWPup.
Here are the exact steps I followed:
Test 1 — Fresh installation (works as expected)
- Fresh WordPress installation
- Install BackWPup 5.6.6
- Click Backup Now
- Check Backups History
Result:
The backup is labeled correctly (not “Scheduled”).Screencast: https://ibb.co/RfQ2XdP
Test 2 — Upgrade scenario (issue appears)
- Fresh WordPress installation
- Install BackWPup 5.0.1
- Trigger a backup using Backup Now
- Upgrade the plugin to BackWPup 5.6.6
- Trigger another backup using Backup Now
- Check Backups History
Result:
The backup created via Backup Now is labeled:ScheduledScreencast: https://ibb.co/cSjWNngK
After performing this upgrade path, I can reproduce the behavior consistently.
This suggests the issue may be related to:
- a migration step
- stored job metadata
- or existing database records created by older versions
I have not yet tested from which intermediate version onwards an upgrade no longer produces this behavior. I only verified the scenario starting from 5.0.1 → 5.6.6.
Please let me know if there is any additional information that would help investigate this further (e.g. database tables, logs, etc.).
- This reply was modified 3 months, 2 weeks ago by josch87.
Hi @saranshwpm,
thank you for taking a look at this.
I tested it again and I can still reproduce the behavior consistently. I’ve attached a screen recording that shows the full process.
What happens on my side:
- I open the BackWPup admin page.
- I click the “Backup Now” button in the top-right corner.
- The backup runs successfully.
- After completion, the entry in Backups History is listed with the type:
ScheduledSo even though the backup was triggered manually via Backup Now, it is still recorded as Scheduled in the history.
Thanks again for looking into this.
Forum: Reviews
In reply to: [BackWPup – WordPress Backup & Restore Plugin] >= 5.0. – Worst NightmareBy the way: Looking forward for someone to fork version 4.1 (GPLv2)!
Forum: Plugins
In reply to: [Check & Log Email - Easy Email Testing & Mail logging] From in headerYes, I did.
Changing the email header helps. It would just be great to test with the standard header that php mailer is using for the installation.Forum: Plugins
In reply to: [Check & Log Email - Easy Email Testing & Mail logging] From in headerI was trying to test if wordpress is sending mails. Unfortunately the plugin used the send to address as send from as well. This is never a good idea because of DMARK/DKIM – even in a test scenario.
The email will not be in any inbox/spam folder because it is denied by DKIM/DMARC rules. Testing not possible. That of course only applies to emails were domain has a DKIM/DMARC rule.
Is there anything else I can provide you with?
Thanks
Aljoscha@reneesoffice Everything is working as expected with 1.2.0. Thank you very much.
There is no open issue in relation to this unfortunately,
Are you refering to issue 837? The current status is “open”. @reneesoffice was able to repliacte the issue.
I am not quite sure what you mean by “refers to the “Property Name”. There is currently no output for the property name at the plugins backend.
- I changed property name of **968-3
- I disconnected Analytics from Site Kit
- Reconneced. Wrong property again: https://prnt.sc/qafqf1
We’ll keep you updated on the progress of the issue being resolved.
Unfortunately I did not hear back from you that the issue is fixed and merged into master.
Problem still exists using WordPress 5.3.1 and Site Kit by Google 1.1.3
Does this mean that it is not possible at all with Facebook to grant access to Developer Apps autonomously of the rights that the administrators have? Or does this just not work together with Flow Flow?
I do not want to use Method #1 because the other person would have complete control over the facebook app. Is this really necessary in order to grant the Facebook Developer app access to all the facebook pages?
http://staging.arbeit-bewegung-geschichte.de/test_the-post-grid/
USER/PW for htaccess: radiusthemeI deactivated all plugins except “The Post Grid”. Seems to be a conflict with the theme.
Thank you very much!
ModSec is not part of the hosting and therefore not active. I sent you a php info so that you can see the current settings and a site health report after updating to WP 5.2 today.
- This reply was modified 7 years, 1 month ago by josch87.
- Reseting all options
- Deleting and reinstalling plugin
- Reinstalling same WordPress version
did not work. Also
define('WP_DEBUG', true); define('WP_DEBUG_LOG', true);did not give out any php errors concerning this problem.
I already created a bug report on your website (ticket 280235) and they forwarded me to this forum. I will open this ticket again.