hoorna
Forum Replies Created
-
@rubyat13, many thanks for your message and the promised fix!
I managed to go back to a fully working Subsribe2 version 10.37. I want to share with other users how I did this. This worked well for me. Of course I don’t know if it works for other users as well as their Subsribe2 database may have been confused by several recovery attempts. But it’s worth giving a try.
- Log out of the WordPress site running Subscribe2 version 10.39.
- Download the Subscribe2 version 10.37 installation (.zip) file using this link.
- Delete the “subscribe2” subdirectory in the “…../wp-content/plugin” subdirectory of your WordPress website. For this, you need to have direct access to the subdirectories of your website, for example via FTP, Filezilla, etc. If necessary, ask your website provider to delete the subdirectory for you.
- Log in to your website. WordPress is now probably complaining about missing and subsequent disabling the Subscribe2 plugin. You can ignore this message.
- In the WordPress menu choose Plugins -> New plugin. Next press the “Upload plugin” button (or something similar; I translated this from Dutch). This button is located at the top of the screen.
- Select the file “subscribe2.10.37.zip” which you downloaded in step 2.
- Press the “Install now” button and then the Activate button.
- You should now have a working Subscribe2 version 10.37.
@rubyat13, I have the same problem with subscribe2 since the last plugin update. The plugin do not send emails anymore; it does not send emails for new posts and either with the menu page “Send email”.
When I send test emails with my email-plugin then the will be sent immediately and almost instantanously delivered in my emailbox. So there is no problem with my WordPress setup nor with the connection to my email provider.
I use this plugin with much pleasure for years and years now it never failed until the latest update. Please help!
@duongcuong96, thanks for the support. I got BackWPup version 3.10.0 working again.
@kpbryce132. I have tried that but the plugins page still tells then that BackWPup is on version 4.0.0 (which is not true). To me this seems not safe. Therefore I disabled the plugin and placed the original 4.0.0 “backwpup” directory (which I had temporarily named to _backwpup) back awaiting for a fix.
Hi Daniel,
I solved the problem. In BackWPup > Settings > Tab: Logs I declared a absolute path. If I declare a relative path then everything is working ok!
Hi Daniel,
Since 6the of June this year BackWPup refuses to make backups again. I think this is after I updated BackWPup to a new version (I do not remember which version).
Again I get the message: “Directory /var/services/web/website/wp-content/plugins/backwpup/logs is not in open basedir, please use another folder.” I do not know what you changed in that update but backing up with BackWPup is not working any more.
In open_basedir I included the folder /var/services/web. I think this is quite right but apparently not enough.
For your information: BackWPup > Settings > Tab: Information gives ‘Log-directory: /var/services/web/website/wp-content/plugins/backwpup/logs/Please help!. I hope you can solve this problem forever.
I am not sure that I understand your reply quite right.
In DocumentRoot I declare “/var/services/web/mywebsite” as the rootdirectory of my website and consequently “/var/services/web” is included in open_basedir. If BackWPup should use DocumentRoot than there are no errors.
The strange thing is that BackWPup finds and uses “/volume1/web/mywebsite” as the rootdirectory of my website which internally points to exactly the same location als “/var/services/web/mywebsite”. This is a problem for me because for security reasons Synology advises not to use “/volume1/web/” in open_basedir. I do not understand why BackWPup finds “/volume1/web/mywebsite” as rootdirectory whereas I explicity declare “/var/services/web/mywebsite” as root.
The workaround worked for me too. Thanks!!
Although I do not have much knowledge about PHP-programmaing, there is one thing I do not understand.
I have configured my website with a vhost configuration (on a Synology NAS). In the vhost configuration file I use the directive DocumentRoot to declare the directory of my website (“/var/services/web/mywebsite”). It seems that BackWPup is not using this declaration. It finds “/volume1/web/mywebsite” for the first part of the temp and the log folder.
Isn’t that strange? Is it possible (and if so should it not be better) to use the DocumentRoot declaration within BackpWPup?
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] HTTP SSL errorI will try it at the end of next week. On this moment it is impossible for me to test.
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] HTTP SSL errorDo you have a solution for this problem? I still (version 3.0.6) get the error which I reported a the beginning of this thread.
Meanwhile I found out that the problem only occurs when I try to start a job immediately. Jobs started by linux-cron (by calling “wget -q -O http://website-name/wp-con.php?doing_wp_cron >/dev/null 2>&1”) are running normaly.
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] HTTP SSL errorDoes nobody recognize this problem and/or have a tip?
Thank you for your quick response. I am using WordPress version 3.3.2 with theme Weaver version 2.2.8.
When I make an new Post (or when I republish an existing Post) then Subscribe2 sends notification emails. When I create a new Page (or when I republish an existing Page) nothing happens although i have selected “Send email for Pages: Yes”.
Of course I am willing to give you more details if you want. Please let me know.
Hi, I am experiencing exactly the same problem as zfriedlander. I have installed version 8.2 and tried also developmentversion 8.3. Notifications for pages (new or old [changed to draft and published again]) aren’t sent. Notifications are sent perfectly with posts.
I hope you will have a solution.