Navigation

Pligg Support

Avatar
Jhawkin

http://www.ParadigmDomains.com
Jeff Hawkins is a Web Guru, Tall Tale Tech Writer and Short Order Cook · Monster Highway Cafe from Middletown, Va. (The Center of the Known Universe)
I'm just about at the point where I need a second webserver and was thinking about off loading the databases to Google Cloud instead which could buy me a year or two right there.

Any experiences, advice or thoughts???? My other option would be a vps server with just MySQL running or a server here at the house running over Comcast (not great).
I tried to post here a few minutes ago and received a Captcha that presented a box to enter my email address with a message about 'suspicious activity from 'this address'.

I just reloaded the Captcha again and it went away.
We need some kind of module that would traverse the stories data table looking for broken bookmarks back to the originating story. This would reduce the number of 'broken' links when Pligg is being used as a bookmarking site.

My thoughts are the module should start from the oldest post (most likely to be, broken, deleted or 'out of date'), run from a cron or pseudo-cron trigger/task and check a configurable number of posts, keep track of it's last checked story and continue from there on each successive cron trigger..

The module should be configurable to either place a failed story into 'upcoming', moderation, discard or else do nothing but email the admin with a link to the story..

The action should also be configurable for counts of failed check attempts as the referenced server downtime could cause a false trigger.
I'm getting ready to try installing the WordPress login plugin / Pligg module again. Hoping to get it working this time.

One caveat is I'm running WordPress in the root directory with Pligg answering from it's own directory via a htaccess redirect. Had to do it this way as some of my sites require WordPress running under multi-site.

I need to know the Pligg 'Salt_Length' and any other tips would be appreciated. If I get it working I'll try to document everything and make that available to everyone who needs it.

I also want to get it working with my older sites running 1.2.2 but the site I'm going to put this on runs 2.0.x.
I'm running Pligg with WordPress in the root directory. Might be a little buggy yet but it's stable enough that I'm getting ready to try multisite within WordPress with Domain Mapping.

My question is:

The WordPress XML site mapper (BWP GXS) isn't picking up Pligg's site maps yet. It should be able to, but I think I need to make a change or two in WP's Function.php.

Any thoughts on this?

BTW: I'm working on some notes about everything I had to do to get this WordPress/Pligg setup running properly. The big change that drives it all is the htaccess file.
URLs are not allowed in titles but the RSS importer allows those which visually conflicts with the actual Title line link. I think the right way would be just to disallow and remove them or else place the whole story into 'upcoming' instead of published where they can be dealt with manually.

Any thoughts or ideas on this would be appreciated.
I'm pulling a lot of feeds from Facebook and sometimes wind up with html entities in the titles which doesn't render properly on display. I know about 'html_entity_decode' but haven't figured out where to put it and the variables involved.
Most of my sites are running WordPress in the root directory (or will be soon) with Pligg in a subdirectory. I did this inorder to be able to run WP as multi-site with the WP domain mapper thinking that down the road I'll possibly be able to multisite the Pligg along side.

I do have one Pligg running several Pligg installs with a single login but haven't got the WordPress to share logins yet. Working on that though! I use RSS to share content from the WP to the Pligg on these sites.

My question is: If you are doing this what are you doing and how deeply tied together are you running this?? I'm looking for ideas to pursue for the benefit of all of us.
Your chosen Domain Name is (well it could be) one of your best ideas. When you have a domain picked out for a new site it's best to go ahead and register it.

I often see people start advertising or using a domain name as part of their Identity in someway before they've registered it. Not a good idea. When I see a decent or interesting domain I check it. If it doesn't give me website I'll run it through a DNS test. If there's no DNS I'll check registration. And sometimes I'll register that domain. You really don't want to lose a good idea/domain name that way do you? Spend the $10.00!!!
I'm seeing a lot of the same spam users appearing in different Pligg installs within my network. I'm starting to think maybe I should start looking for a network wide anti-spam system for my Pligg installs.

I use SFS and Akismet already and don't want another public solution. What I'd like is a simple killspam in one Pligg to traverse the whole network.

Anybody have any ideas?