twoenough
Forum Replies Created
-
Btw, as we were noticed, plugin was taken down because worpdress suddenly decided that autoblogging plugins are not good enough for their directory. It might just been one of the lame and envy competitors that complained, who knows.. and who cares… Anyway, we do fine on our own, plugin is still free to download, just google autoblogging and you will find it (you can’t really miss it since 6-7 out of first 10 results are about it. Must be a sucky and buggy plugin…). Or get it from https://bit.ly/autoblogging-plugin
You are so lucky stupidity does not hurt…
@sailpilot: you are generally right, just that sometime people don’t know what they are doing and talking and what they are pointing out are not software problems but issues caused by their lack of knowledge, not reading manuals or simply because they try to push another plugin by bashing the competitors.
I won’t ask you why you are using such a bad plugin, that is another story :). I can tell you though that the issue was reported a couple times before, by email, and that there are at least 1000 active users of the free plugin. Anyway…
That issue usually happens after using the Lite plugin and then the full one (i don’t know any case when the error shows on lite plugin update, but may be possible). It is fixable from phpmyadmin. I will try to explain you how to fix that yourself.
Go to phpmyadmin and select your wordpress database on left menu.
When you see tables list (also on the left menu), click on wp_multipressContent
On the main screen click on Structure tab at the top. That will show you the list of fields in the table. As the error say, you have one missing field so you need to add it.
At the end of that Structure page you have something like this: Add 1 field(s) At End of Table At Beginning of Table After.
Just leave as it is (default selection should be add 1 field at end of table) and click button Go
A new page will open with some form.
Type “article_limit” (without quotes) in the field name (first field). Then make this settings: Type: INT, Length/Values: 11, Default: None.
Leave all other fields empty and then click Save button.
That is all.. As far as i know all other people been able to fix this themself.
@dadaas, should we take it that you are not a serious webmaster?! It looks like you are using our plugin instead of those aged ones you praise.
As about our refund policy, we offer a 100% free two weeks trial. That is enough time for any serious webmaster to decide if the plugin worth pay for or not. What you think is better, a 14 days refund policy like wprobot has or a fully working and free 2 weeks trial?!
@sailpilot, looks like you are out of luck. Unless you know php and can fix wp o matic yourself, you may have to pay for a plugin that will fix the other plugin bug. ??
@everybody else: that happens when you are taking advices from people that have no idea what they are talking about… Do your own due diligence and don’t listen all the trolls…
Tib, try latest version. Email us if you still have issues.
Ok, so tell me. What is the cronjob command that you need to run with wprobot to launch the autorun?
You were not sent to wprobot for help. You were only informed that is not only Multipress that has that auto-run issue but wprobot and other scripts too, because at some point in your forum post you implied that wprobot would worked better.
The file that wprobot tells you to run via cron is not part of their features but a standard wordpress file, wp-cron.php.
I can confirm this as I installed this on a totally clean wordpress 3.0 install, and it behaves in exactly the same way.
So it appears that this plugin has some issues with certain utf-8 characters. Whenever a RSS feed contains one of these it truncates the feed at that point.
Can you post or email us examples of truncated articles + link to original post?
The issue is not necessarily with the plugin: https://core.trac.www.ads-software.com/ticket/11175. They say that was fixed in 3.0 but we can’t guarantee, we can only try find a workaround.
Forum: Plugins
In reply to: [Plugin: MultiPress Autoblogging plugin] Error in init.phpwell.. that is weird. That error is about some internal logs, should not mean anything, or better say not cause any issues. It may be some conflict with another plugin.
If you want e can have a deeper look, email us your blog url and some temp access.
Forum: Plugins
In reply to: [Plugin: MultiPress Autoblogging plugin] Error in init.phpcan you paste full error? It say …at line… but no line number
Forum: Plugins
In reply to: [Plugin: MultiPress Autoblogging plugin] Error in init.phpTib, Make sure you upload in binary mode and your host has Zend Optimizer installed. Let me know if problem persist.
ONE link in a post is NOT link stuffing! There is a paid version of the plugin as well for anyone that does not like ONE link in a post. Your warning is silly and not based on any facts. Don’t assume what we could get or not, you have no idea about that.
Recommending wp-o-matic against multipress is at least funny and it will surely not help anyone.
Beside wp-o-matic being not updated for more then 2 years and reported with many issues like making duplicate posts, is also not even doing 15% from what our multipress can do. Wp-o-matic limited to rss only.
You are probably kidding. I don’t want to think that you really believe what you are saying.
“..links to affiliate sites and websites that are not allowed to be linked on a website with adsense code.”
Since when you can get banned from adsense for linking to affiliate sites?! Or any other site as a matter fact (excluding porn or illegal sites)…
That is a very good joke :)).
Anyway, seriously now, first of all there are no affiliate links added in the posts, and second, the links that are added are to legit sites, mostly blogs.
Are you CC owner or just paid to make them good press?! :))
Forum: Plugins
In reply to: [Plugin: MultiPress Content] DuplicatesThe error is not because wp 3.0, plugin will work fine there.
The issue is with your server setup. For some reason curl can’t set options. You probably have php running in safemode. You should talk to your host support, is a sever related issue.