Jump to content

Robert

Admin
  • Content count

    177
  • Joined

  • Last visited

Everything posted by Robert

  1. Can The Unencoded Version Still Be Downloaded?

    Selena, I have PM'ed you.
  2. The following is a list of enhancements/customizations that would make the script itself be more adaptable to particular areas of the business. Financially, it makes sense that MB focuses more energy on their flagship Tube site, which makes the TGP script less of a priority, understandably. But this will serve as an ongoing feature request that we, as a community, can hopefully get accomplished. Niche/Channel/Models Specific Ads -- there are currently templates in place that allow you to include ads on a per sponsor basis. But it would be nice to be able to define ones to appear on specific niche pages, model pages, etc. Bad Gallery Checker -- a cron task that will check for, and disable, galleries and gallery links which have errors (thumb count changes, 404, 403, redirected, etc). Plug system -- this would include letting registered users submit plugs, see the clicks on the plug, etc. A CSV plug import system for registered Premium users and admins would be great. Plug Display -- this would allow admins to specify a max number of plugs per cronPublish, for example, 3 galleries plus 1 plug. Payment Gateway -- to permit payment of plugs, advertisements, etc. Date Scheduler -- The ability to schedule the date for a gallery, plug or link to be published. Also, the END date for a plug. Notification System -- for plugs owners and gallery owners where they can be notified if their plugs are disabled or expired. A reporting system to tell Premium Members how many clicks their plugs received. Export Galleries -- The ability to export galleries into an xml file, and do it by criteria such as status (published, approved, existing), the paysite, the user, the model, etc. MechBunny TGP Owners who have other suggestions, feel free to let us know, or post them here and we'll pin these as well.
  3. Cant create getscorecash galleries

    I don't think this is specific to Arylia. Rather, it could possibly be that Score is not utilizing anti-leech/anti-hotlinking in their htaccess (this script does not use a "browser" retrieve the images, so there is no header information sent. If there is a restriction in place to require the referring URL to the image being spidered, it would not show as being for the gallery URL. Having said that, I think it's more to do with the screenshow script. If you look at this gallery: http://gallys.40somethingmag.com/images/DesiFoxxXXX_22009/ If you mouse over the first thumb, it shows the link to the big pic as: http://gallys.40somethingmag.com/images_content/DesiFoxxXXX_22009/01.jpg However, if you right click on the thumb and choose to open link in new window, the ACTUAL url to the larger pic is: http://scoregroup.vo.llnwd.net/o37/40somethingmag/images_content/DesiFoxxXXX_22009/01.jpg Note, the URL's are completely different. My best guess is that the screenshow is masking the actual big pic location, which means arylia is looking for an image at a URL that doesn't really exist.
  4. MechBunny TGP Suggested Improvements

    Nice ideas. Will add them. FWIW, the programmer doing the TGP Script for Mechbunny has this URL (I sent it to him). I've asked for a quote for other things as well.
  5. link rel="canonical"

    No problem. Glad its working for you.
  6. link rel="canonical"

    JJ... the way I do it for the lemmecheck galleries are: <link rel='canonical' href='<?php echo 'https://www.mydomain.com' . trim(strtok($_SERVER['REQUEST_URI'], '?'),'index.html' ); ?>' /> Note, replace "mydomain.com" with the root domain where your arylia galleries are displayed. I also like my galleries clean with no index.html, index.php at the end, so I trim them here. Put that in your template, and then re-generate a gallery, view source and then tweak as needed.
  7. Intro One of the biggest hurdles with WordPress for many site owners is to try and maintain it, keep it updated, etc. But there are a few efficient ways of keeping things updated in a fairly automated fashion. This post will serve a reference point for that. Use at Your Own Risk! This script is offered free of charge and is intended as a guideline only. If in doubt, speak with your system administrator or programmer. And ALWAYS backup -- at least at first -- before using it. Use this at your own risk. FWIW, we use this regularly and are just sharing it here so that others may find it useful. Things We Need You need SSH access to your server. You need the ability to create cronjobs You need the ability to use wget and tar commands The ability to execute shell scripts (bash script) mysqldump is an added bonus if you have it available. ** In the case that you have managed hosting, this guide can also be used by your hosting provider to implement for you. Creating a Central Location The idea here is to keep a current copy of WordPress, any plugins you use, and any themes in a single centralized location. For our purposes here, we will use the following format. Create your own structure, or feel free to use the one below. If you use a custom structure, be sure to edit the script to reflect your own structure. /home/upgrades/repo/ /home/upgrades/repo/downloads /home/upgrades/repo/plugins /home/upgrades/repo/themes /home/upgrades/repo/wordpress Upload all of your common plugins in the plugins folder and themes in the themes folder Creating the Script In a plain text editor, like EditPad, you can paste in the following as a guide. #!/bin/bash # ########################################################## ## REMOVE ALL STANDARD PLUGINS AND WORDPRESS FILES # We cannot remove themes cause of the way they do logins # so themes will need to be downloaded manually. Plugins use # version numbers in their files so cannot download those. ## ########################################################## rm -rf /home/upgrades/repo/wordpress # ########################################################## ## DOWNLOAD, UNPACK and PREPARE WORDPRESS WORDPRESS ## ########################################################## wget -P /home/upgrades/downloads/ https://wordpress.org/latest.tar.gz tar -xzf /home/upgrades/downloads/latest.tar.gz -C /home/upgrades/repo/ # ########################################################## ## DELETE OLD AKISMET / COPY NEW AKISMET TO PLUGINS FOLDER ## ########################################################## rm -rf /home/upgrades/repo/plugins/akismet cp -apr /home/upgrades/repo/wordpress/wp-content/plugins/akismet /home/upgrades/repo/plugins/ # ########################################################## ## DELETE FILES AND DO SOME HOUSECLEANING ## ########################################################## rm -f /home/upgrades/downloads/* # ########################################################## ## BACKUP ALL DATABASES ## ########################################################## mysqldump --user=YOURDBUSERNAME --password='DBPASSWORD' --host=localhost DBNAME01 > /home/upgrades/backups/sql/DBNAME01.sql mysqldump --user=YOURDBUSERNAME --password='DBPASSWORD' --host=localhost DBNAME02 > /home/upgrades/backups/sql/DBNAME01.sql mysqldump --user=YOURDBUSERNAME --password='DBPASSWORD' --host=localhost DBNAME03 > /home/upgrades/backups/sql/DBNAME01.sql # ########################################################## # # UPDATE WORDPRESS SITES # Replace Site01.com with your own domain. Same with Site02, # Site03, etc. You can have as many sites as you like. # # Also, be sure you ONLY DELETE THE THEME PARENT FOLDER. # DO NOT DELETE your child theme. This script assumes you # use Child Themes which you should always use anyway. # # ########################################################## # FIRST WORDPRESS SITE rm -rf /home/SITE01.com/htdocs/wp-admin/ rm -rf /home/SITE01.COM/htdocs/wp-includes/ rm -rf /home/SITE01.COM/htdocs/wp-content/plugins/ rm -rf /home/SITE01.COM/htdocs/wp-content/themes/THEME-PARENT-NAME/ rm -rf /home/SITE01.COM/htdocs/wp-content/themes/twentyfifteen/ rm -rf /home/SITE01.COM/htdocs/wp-content/themes/twentyseventeen/ rm -rf /home/SITE01.COM/htdocs/wp-content/themes/twentysixteen/ rm -rf /home/SITE01.COM/htdocs/wp-*.php rm -rf /home/SITE01.COM/htdocs/xmlrpc.php cp -apr /home/upgrades/repo/wordpress/* /home/SITE01.COM/htdocs cp -apr /home/upgrades/repo/plugins/* /home/SITE01.COM/htdocs/wp-content/plugins/ cp -apr /home/upgrades/repo/themes/* /home/SITE01.COM/htdocs/wp-content/themes/ # SECOND WORDPRESS SITE rm -rf /home/SITE02.COM/htdocs/wp-admin/ rm -rf /home/SITE02.COM/htdocs/wp-includes/ rm -rf /home/SITE02.COM/htdocs/wp-content/plugins/ rm -rf /home/SITE02.COM/htdocs/wp-content/themes/THEME-PARENT-NAME/ rm -rf /home/SITE02.COM/htdocs/wp-content/themes/twentyfifteen/ rm -rf /home/SITE02.COM/htdocs/wp-content/themes/twentyseventeen/ rm -rf /home/SITE02.COM/htdocs/wp-content/themes/twentysixteen/ rm -rf /home/SITE02.COM/htdocs/wp-*.php rm -rf /home/SITE02.COM/htdocs/xmlrpc.php cp -apr /home/upgrades/repo/wordpress/* /home/SITE02.COM/htdocs cp -apr /home/upgrades/repo/plugins/* /home/SITE02.COM/htdocs/wp-content/plugins/ cp -apr /home/upgrades/repo/themes/* /home/SITE02.COM/htdocs/wp-content/themes/ # THIRD WORDPRESS SITE rm -rf /home/SITE03.COM/htdocs/wp-admin/ rm -rf /home/SITE03.COM/htdocs/wp-includes/ rm -rf /home/SITE03.COM/htdocs/wp-content/plugins/ rm -rf /home/SITE03.COM/htdocs/wp-content/themes/THEME-PARENT-NAME/ rm -rf /home/SITE03.COM/htdocs/wp-content/themes/twentyfifteen/ rm -rf /home/SITE03.COM/htdocs/wp-content/themes/twentyseventeen/ rm -rf /home/SITE03.COM/htdocs/wp-content/themes/twentysixteen/ rm -rf /home/SITE03.COM/htdocs/wp-*.php rm -rf /home/SITE03.COM/htdocs/xmlrpc.php cp -apr /home/upgrades/repo/wordpress/* /home/SITE03.COM/htdocs cp -apr /home/upgrades/repo/plugins/* /home/SITE03.COM/htdocs/wp-content/plugins/ cp -apr /home/upgrades/repo/themes/* /home/SITE03.COM/htdocs/wp-content/themes/ Saving and Uploading Save this script as upgrade.sh and upload it to the /home/upgrades/ folder created in the first step above. The Script Explained Much of it is documented throughout already, but we will explain a few of the sections. The first section deletes the old WordPress archive previously downloaded. The next section grabs the latest version of WordPress, downloads it, extracts is, and then saves it in the /home/repo/wordpress folder. This ensures you have the latest copy. Akismet. Because WordPress ships with the latest Akismet embedded, we need to copy it to to our plugins folder. This routine does that. This routine deletes the downloaded tar file from the downloads folder. Backing up the databases. Never a bad thing to do before upgrading. Backed up databases are stored in the /home/upgrades/backups folder. Update each WordPress site. Note that the first part of this section for each site deletes the wp-admin, wp-includes, the plugins folder, the standard themes AND the parent theme folder. We specify the themes for each site to ensure we are not deleting the CHILD theme we are using. We delete all core WordPress files to ensure that no orphans are left behind. This also ensures you have a clean original copy should any of your files ever get hacked. The second half of each of the site updates involves copying the fresh copy of WordPress we just downloaded and extracted, as well as the plugins and themes we downloaded and placed into the respective folders. Executing the Script Here you have two choices. You can either execute the script regularly via cronjob, or simply ssh to your server as follows. Note, the ">" represents a command prompt: > cd /home/upgrades > ENTER > bash ./upgrade.sh > ENTER That's it. The script will go through and replace all of the core WordPress files and folders, as well as your plugins and themes with the newer versions located in your "repo". The entire process is fairly quick. We can upgrade about 60 sites this way in less than a minute or so. Download the Script If you'd prefer a pre-formatted copy, you can download the above file right here: upgrade-example.sh Updating Sites on Multiple Servers This is easily achieved by having your host install keys on each server you want to communicate with, and then using rsync to replicate your "/home/upgrades/repo/" structure. Then just customize the script to that server's database names and site specific information.
  8. TGP and MGP Sites

    Below is a list of a sites where you can submit picture and/or video galleries. Not all have extensive traffic, but they are reliable nonetheless. Paid Submits Elephant List - http://www.elephantlist.com - Paid account. Old school text tgp and the owner is easy to work with. Library of Thumbs - http://www.libraryofthumbs.com - Paid account. Real easy guy to work with. Pinkworld - http://www.pinkworld.com/ - Paid account. The traffic is consistent and the owner really easy to work with. Free Submits FreeOnes - http://www.freeones.com/ - Great site, pornstar specific, and quality traffic. Adult Fan Clubs - http://www.adultfanclubs.net/ - Comprehensive directory. Well worth getting galleries archived in here. BabePedia - http://www.babepedia.com Very easy to use. Submit one link or many via csv upload. Pornstar specific. Barelist - http://www.barelist.com - Another great site, pornstar specific. The Hun's Yellow Pages - http://www.thehun.net/ - Legendary site. Fetish does well here. Outlaw TGP - http://www.outlawtgp.com - Free to submit. Paid option available. Run by a great old school guy.
  9. Arylia handling of HTTPS linked images

    Hey Troy... long time no talk. Hope you've been keeping well. Thanks for the share! -Robert
  10. Is It Possible To Setup A Cdn?

    Honestly, I have not looked at it. At first glance, it would seem to me that you need to modify the script to store the images on the cdn after it creates the gallery, then have the have the templates reference the cdn location. Almost certainly you would to have it modified by a programmer.
  11. reduces image quality?

    Perfect. Thanks for the info.
  12. reduces image quality?

    Hmm, ok, I'll have to look closer -- I'll try to get to it a bit later today. But my guess is one of the routines then in the general functions, perhaps the "Queue" file will have hardcoded image quality values. So you might want to look there. I would start looking for hardcoded quality settings of 90 to 95 in the files, using searches for things like "truecolor", "resampled", "imagecreate" etc -- the ones that would be local commands for imagemagick
  13. reduces image quality?

    Try this. Open the file /app/functions.inc.php On, or about, line #614, locate the following routine: if ( $t == 1 ) { $img_src = imagecreatefromjpeg( $sourcefile ); $img_dst = imagecreatetruecolor( $iw, $ih ); imagecopyresampled( $img_dst, $img_src, 0, 0, 0, 0, $iw, $ih, $is[0], $is[1] ); if( !imagejpeg( $img_dst, $destfile, 95 ) ) { exit( ); } } Change it to this: if ( $t == 1 ) { $img_src = imagecreatefromjpeg( $sourcefile ); $img_dst = imagecreatetruecolor( $iw, $ih ); imagecopyresampled( $img_dst, $img_src, 0, 0, 0, 0, $iw, $ih, $is[0], $is[1] ); if( !imagejpeg( $img_dst, $destfile, 90 ) ) { exit( ); } } Note the slight difference. The original value is "95" for image quality. In the second example, I changed it to 90. Save it Backup your original file, then upload the newly saved one. You may need to do some trial and error to figure out the best blend of quality versus file size. Let me know if that works for you. I'm not sure if that's it or not. I just took an educated guess from a quick look, but I think that's where you can change the value of the resampled images.
  14. Questions about Arylia

    Hello Ty: PM me more details on the attempted transaction. I will pass it along to the guy running the Arylia site for you. The version we modified and provide for registered users, does work on PHP 5.6 -- we use it ourselves on a php 5.6 environment, so we know it works. Arylia is NOT a CMS. You basically design your own template, and then place image size values in the templates where you want the thumbs to appear, and Arylia will crop according to those template values. Thus, you can create any type of template you want. Arylia simply places the thumbs inside the template you design. Here's an example gallery we just created using Arylia in a php 5.6 environment -- it is responsive. The "design" was done with Wordpress and we simply extracted what we needed to make a standalone gallery template. Arylia makes this sort of things incredibly easy. Of course, you can use any design you like, or that you have a graphic designer make.
  15. Moving Arylia

    My pleasure, good luck.
  16. Moving Arylia

    morf: when moving hosts, you will need two things, the database dump and a tar file of the arylia folders. It's actually pretty easy if you have root access: Login via ssh as a root user and dump your database: mysqldump --user=root --password='whatever' --host=localhost databasename > databasename.sql Password is whatever your root mySQL password is, and databasename.sql can be anything. It's just the full sql dump of your database. Next, tar your arylia folder keeping all permissions intact. Do this from ROOT user: tar -cpf arylia.tar /path/to/arylia/folder Download the tar file and the sql file you created. sFTP to the new host and upload both files. Be sure to place the arylia.tar in the root of the domain's htdocs/www folder where it was previously. Create a database with the same name as the original. Switch to ROOT user and import the database as follows: mysql --user=root --password='whatever' --host=localhost databasename < databasename.sql While still in ROOT, navigate to the folder you uploaded the tar file and extract it like this: tar -xpf arylia.tar Once done and your DNS is updated, login to the arylia admin and verify the paths to things like imagemagick and CLI to ensure they are correct. That's all there is to it. If you don't have root access, you could simply ask you old host to dump your database and tar the files up as noted above. And then send them to your new host and ask them to create the new database, untar from root and import the database. It's really not a lengthy process at all. The reason you should do it from ROOT for the tarring is because Arylia creates files, like the galleries as being "owned" by the server (user nobody, user apache, etc). You won't have access to edit them or do anything with them since the file ownership is not user specific. One thing to make absolutely sure of before you move is that the new host meets the minimum requirements. You can find that info here: FWIW, the version we have for download is being used by us on php 5.6 with zero issues at all. Good luck.
  17. Purchasing Arylia License

    sirrotica, you can login to the Arylia portal at the link below, using the username and password you received when you first purchased the software: http://www.arylia.com/users/index.php?action=showLogin Once you get the password, you can download the script again here: If you have any problems, let me know.
  18. Zip creaion izzue

    Hey Morf: To the first question, I know it seems obvious, but an Error 500 is a server error that usually means something isn't configured properly to run with the script. Check to make sure the location of the zip utility in your admin General Settings matches that on your server, and that the tmp folder in your Arylia directory is set correctly, along with 777 write permissions. To the second question, no, the password did not change. You mean to download the php 5.3.x fix? Shoot me a PM and we can get it cleared up for you. -Robert PS: sorry the reply is late. I had notifications turned off for some reason and never knew there was a post waiting for an answer.
  19. Who Are Cherry Pimps? Cherry Pimps is quietly becoming one of the most well-rounded affiliate programs in the adult space, providing adult webmasters with both an abundance of tools, consistently updated websites to promote, and a team of highly qualified personnel to help you achieve maximum conversions. Just as importantly, they never miss a payment which is becoming almost a rarity in the adult affiliate business over the last few years. Suffice it to say, if you are already promoting Cherry Pimps, then you understand this viewpoint very well. If you are not already promoting Cherry Pimps, then you are leaving money on the table. Cherry Pimps Approach Cherry Pimps is headed by a team of smart people, and an extremely smart man at the head of the table, Avalanche (Jack). Over the past few years, they have assembled of team of experienced industry professionals who have excelled in their respective fields, from designers to marketing and affiliate manager specialists, and they are all there to help make you -- and them -- a maximum return on investment. Beyond the standard tools for adult affiliate webmasters -- fhg's, downloadable content, banners, etc -- Cherry Pimps' business model includes a direct relationship with their Webcam Platform, Wild on Cam. Models who are hired, or contracted to appear for shoots, are often also hired to do live cam shows. And these shows happen daily. When a person you refer to CherryPimps joins, they not only get access to the huge library of content, they also gain access to the live shows, including the live show recorded archives. Affiliate marketers can use their custom webcam tool to create a live countdown image, that literally counts down the hours and minutes to the next live show. This is an extreemly effective tool for affiliates to place on their sites. Solo Model and Porn Star Sites In addition to the above, Cherry Pimps also features the official sites of numerous models and pornstars, and they are constantly growing. Affiliates can market one, or all of the official sites, or their respective live cam shows, or the main hub itself, the CherryPimps.com site. This effectively provides a multitude of methods and landing pages from which to match with your site's demographics. Stop Leaving Money on the Table After nearly 20 years in this business, Cherry Pimps has emerged as a program that has caught my eye, and have become the site we actually want to promote regularly. The attention to detail is impressive, as is their constant striving to improve on their already high standard. Speak to someone at Cherry Pimps today. They welcome affiliate inquiries as well business inquiries for ongoing relationships. Thanks us later. Contact Information Affiliate Program: http://nats.cherrypimps.com/ Affiliate Director Nancy Moore [email protected] ICQ 460-308-073 Skype nancym00re Webmaster / Content Manager Kellie [email protected] ICQ 216-375-050 Skype kellie_az Program Director Avalanche [email protected] ICQ 291-436-730 Skype CherryPimps
  20. Fix required for php 5.4?

    Just to add to this, we are running it on PHP 5.5.3 as well with no modifications needed.
  21. Resetting Your Admin Password If you have forgotten or misplaced your Blogs Organizer admin password, there is no way to retrieve it. However, you can reset it by creating a new password. 1. Create a file named resetpassword.php and enter the following content: <?php require_once 'boinfo.inc.php'; $pass=md5('newpass'); mysql_query("UPDATE bosettings set password='$pass'"); echo '<center><b>DONE</b></center>'; ?> 2. Save this file and upload it your Blogs Organizer Installation folder. 3. In your web browser, open the URL where you uploaded this file. This will reset the password to a default. 4. Login to your Admin area using the TEMPORARY password newpass 5. In your admin area, go to General Settings -> Change Password and enter in your new password. 6. Delete resetpassword.php from your server.
  22. Customizing and Using the Archive Calendar Feature This is a quick guide to customizing the output and appearance of the Archive Calendar on your Blogs Organizer Blog. If you have basic CSS knowledge, then you can customize this fairly easily. In your Blog Template, there is a %%CALENDAR%% variable which when inserted into your template produces a calendar on your blog. The calendar function of Blogs Organizer uses the following predefined classes. Simply style each of these in your CSS stylesheet to customize the output to suit your tastes. cal_table - this css class refers to the whole calendar table. cal_td_back - this css class refers to the column having the link to browse back the archives, right on top at the calendar table. cal_link_back - this css class refers to the link for browsing the archives back. cal_td_forward - this css class refers to the column having the link to browse forward the archives, right on top at the calendar table. cal_link_forward - this css class refers to the link for browsing the archives forward. cal_td_header - this css class refers to the top middle header calendar column, saying the month and year of the current archives displayed. cal_td_week - this css class refers to the columns having the week days displayed. cal_day - this css class refers to the columns having the month's days displayed in the calendar. cal_day_ev - this css class refers to the columns having the month's days displayed in the calendar, but exactly the day's that have archives. cal_link - this css class refers to the links for the archives of a certain day from the calendar. Note that the days that have archived posts are being displayed as links only!
  23. Using RSS Sidebars This brief guide explains how to use the RSS Sidebars feature of Blogs Organizer. This feature lets you display the contents of an RSS feed in your blog's sidebars. Add RSS Feeds to your Blogs Organizer. To do so, login to your admin area and select RSS Feeders -> Add New Once your have RSS Feeds added, proceed to RSS Feeders -> RSS Sidebars Select the feed you would like to use. Select the number of entries you would like for your blog's sidebar to display. Choose the Date Format. Define a template to determine how your links will be displayed. Click the ADD button to submit the form. Upon adding it, take note of the RSS Sidebar Number. You will need it later. Depending on if your blogs are "Regular Blogs" or "Remote Blogs", navigate to the proper one and select the blog that you would like to include the RSS Sidebar you created. Click to Edit the blog and in the Main Blog Template. To add the RSS Sidebar, place %%RSS_SIDEBAR_NUM%% where you want it to appear and change NUM to the unique RSS Sidebar number you created in Step 2 above. Save the blog settings. TIP: You can use multiple RSS Sidebars on your templates, if you choose to do so.
  24. Remote Blogs Options and Management The Remote Blogs section is a drop down menu that is available to you when you login to your Blogs Organizer admin area. From this section you maintain your remote blogs. What Is A Remote Blog? A remote blog is considered any kind of blog you have that is not created and operated by Blogs Organizer. Such remote blogs can be blogs you have running with other blogging scripts like WordPress, Drupal and etc. OR blogs hosted at remote hosting services. With Blogs Organizer you can easily post new posts to these kind of blogs and even schedule your posts for automatic publishing. Services To maintain a remote blog in Blogs Organizer, first you need to specify what type that blog is (WordPress, Blogger, etc.) In this section you maintain your blog basis, so Blogs Organizer will know how to treat the blog itself. Accounts To maintain a remote blog you must specify an account containing your blog at the blog service. This is used and for authentication to the blog software that is running the blog itself. In this section you add/manage your remote blog accounts, by detaching the accounts to your remote blog services. Right after you add your account, you can scan the account for blogs and add them to Blogs Organizer database, so you can use them. Blogs This is the list with your remote blogs. From here you can maintain the remote blogs and post to them.
  25. Blogs Organizer RSS Feeders

    RSS Feeders The RSS Feeders section is a drop down menu that is available to you when you login to your Blogs Organizer admin area. From this section, you can add to Blogs Organizer your urls for feeds from which you want to automatically feed your blogs. Just enter the feeds urls and define which blogs which feeds to read and Blogs Organizer will automatically crawl those feeds and insert their contents as posts to your blogs. Add From here you add your feeds urls. One per line. Manage From here you manage your feeds. You can edit/delete/deactivate any of your feeds.
×