Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - forumadmin

Pages: 1 ... 4 5 [6]
Announcements / StatComm 1.6.60 is out
« on: May 01, 2012, 06:03:33 AM »

We added geolocation and other stuff you can read on the blog.

Thanks everyone, stay tuned...
And enjoy the day.

Announcements / StatComm 1.6.52: released to solve trademark issues
« on: May 01, 2012, 06:00:31 AM »
This upgrades provides a solution to the current trademark issues with Wordpress.
You can read more about it on the blog
Also, the forum will be moved soon, since we got a new domain:
Thanks everybody for your support!

Announcements / StatComm 1.6.50 is out
« on: May 01, 2012, 05:58:01 AM »

Announcements / StatComm 1.6.40 is out
« on: May 01, 2012, 05:56:38 AM »

Hi perfphysio, the def folder is under the plugin installation.

If you install from the plugin panel the default name folder would be statpress-community-formerly-statcomm/def.
 If you install the plugin manually, the folder would be  plugins/your-folder-name/def.

Best Regards

Feature Suggestions / Re: Ip linked to stopforumspam?
« on: April 22, 2012, 12:52:51 PM »
Good idea. We're in process of integrating StatComm with api system to detect potential spamming ip.
It could be easy to implement.
Best regards


Announcements / StatComm 1.6.31 is out
« on: April 12, 2012, 06:14:54 AM »
This patch release solve a little problem when downloading the user agent database.
Also we found that our solution, although correct implemented does not scale very well. We are currently designing a a way to get the uas (User Agent String) database in a more reliable way.
More on this topic on the main site
Thanks to all and enjoy the day.

Announcements / StatComm 1.6.3 is out
« on: April 09, 2012, 09:27:05 AM »
Statcomm 1.6.3 added a new API for retrieve user agent information , improved overview and fixes.

You can read about it in WordpressReady site
Enjoy the day!

Announcements / StatComm 1.6.2 Released
« on: April 05, 2012, 07:26:43 AM »

StatComm version 1.6.2 was released, focused on code stabilization and adding  some improvements.

You can read about it on WordpressReady blog.

Enjoy the day.

Announcements / StatComm: RoadMap
« on: March 28, 2012, 08:37:45 PM »
I published the StatComm Roadmap on the blog.
Thanks for your support.

I'm happy to announce the Availability of Statpress Community Plugin, a statistics plugin for Wordpress.

StatPress Community (StatComm) is now available directly from Wordpress Repository or from the Download Page

Feel free to download and test the plugin.

The readme.txt included explain details about this first version
Code: [Select]
=== Plugin Name ===
Contributors: WordpressReady
Donate link:
Tags: stats, statistics, widget, admin, sidebar, visits, visitors, pageview, referrer, spy
Author URI:
Plugin URI
Tags: stats, statistics, visits, visitors, pageview, referrer, spy
Requires at least: 3.0
Tested up to: 3.3.1
Stable Tag: 1.6.0

Real Time Statistics on your blog, collecting information about visitors, spiders, search keywords, feeds, browsers, OS and more.

== Description ==

StatPress Community (shortened to **StatComm** from now on) provides Realtime Statistics on your blog, collecting information about visitors, spiders, search keywords, feeds, browsers, OS and more.

Once the plugin has been activated, it will immediately starts collecting information. **StatComm** provides many views to analyze the incoming users on your blog, and also spy tools to find out their procedence. For users of other StatPress plugins variations, it provides a well known feature set and information.

This RELEASE version is aiming to provide for starters bloggers an unique way to understand what's going on with your traffic.

== Installation ==

* Go to Plugins > Add New for searching plugins
* Search for StatPress Community
* Click on Install Now under StatPress Community
* Activate it. The StatPress Comm menu will appear near the bottom of the admin page. The plugin starts collecting when you activate it.
* Customization? Go to the Options page

Important note: **StatComm** does not conflict with any Statpress versions. Moreover, this plugin should be running fine side by side with
any Statpress alternative(although not recommended)

== Frequently Asked Questions ==

**StatComm** is a giant rewrite of StatPress, a statistics plugin, and it will provide on the following versions a truly way to update from many unsupported StatPress plugins variations. A detailed milestone is under way in the main site. **StatComm** is currently under development, providing support and appreciating the feedback from his starting community.

It also includes widgets for adding to the sidebar (and even a PHP way if you can't use widgets). In this early stage, this feature is
under revision, meaning its internal functionality could change and expand in following versions.

= Multilanguage =

**StatComm** is translated to English, Italian, Spanish, French, German, Russian, Norwegian, Dutch, Brazilian, Turkish and Swedish!
Also, there will be an unified effort to stand out all contributors.
If you think you can contribute to translation/develop/economic/design or other aspects, please be in touch to be on board of the contributor list.

= Where can I get help? =

* Please visit the <a href="">WordpressReady site</a> for news and plugin insight, and also
the <a href="">WordpressReady forum</a> the place for plugin support.
The plugin also includes a help reference to starters and important information on advanced topics.

= Where is the information stored? =

* **StatComm** relies the information storage in a few options and a table (**statcomm** postfix)

= Is there an uninstall? =

* The current release does not have a proper uninstall option although this is on development. Next versions will deal in this aspect.
It means that the table generated won't be deleted during plugin's deactivation nor options.

= How can I migrate my data from version of [Statpress plugin variation here] to **StatComm**? =

* This release version doesn't provide a way to implement a migration, though this issue has heavily analyzed from early stages. **A migration path is under way**, please look for <a href="">WordpressReady site</a> and also <a href="">WordpressReady forum</a> for further questions.

= Are you providing support for other Statpress plugin variations? =

* If you are using different older/unsupported Statpress variations, **StatComm** is the way to go , since this plugin includes all the enhancements of older an outdated Statpress version/variations. To clarify, there is NO support for those plugins.

== Screenshots ==


== Changelog ==

V1.6.0 First Release (2012-03-23 06:34 -3GT)

* Conversion to OOP (Object Oriented Programming)
* Heavy refactoring: no more prefixes all around.
* First-stage documentation towards Javadoc standard (work in progress).
* First round bug-squashing.
* First round deprecated-code clean.
* Recode to avoid conflicts with other Statpress versions/variations.
* Export problem missing field corrected

Bugs and Fixes / Appropiate way to make a post reporting a Bug
« on: March 18, 2012, 01:36:23 PM »
I would appreciate if you find a problem to provide me the following information:
  • WP Version used in your blog/site
  • Plugin version
  • Brief explanation when or in what condition the bug is produced
  • Anything you consider valuable to help you

Troubleshooting / Introduction
« on: March 18, 2012, 01:32:54 PM »
Hello users, I recommend taking few moments to read the readme.txt file included with the plugin to understand how the plugin works.  Thanks!

The plugin has been release and you can get it from Wordpress Repository in the following link:

The following lines is the readme.txt itself:

Code: [Select]
=== Text to Custom Field ===
Contributors: WordpressReady
Author URI:
Plugin URI
Tags: xmlrpc,custom field, field, post
Requires at least: 2.9
Tested up to: 3.3.1
Stable Tag: 1.1

Allows adding custom fields from ANY desktop blog editor even if the editor can't support custom fields!
They are created after publishing/updating.

== Description ==

The plugin works similar as shortcodes with important differences:
* It looks for any tag in the post with the following format: **{cf your_custom_field_name=your_custom_field_value}**
* For any tag found, it create a custom field for that post.
* The tag is erased from the post.

= How to use =

Type in anywhere in a post:
{cf your_custom_field_name=your_custom_field_value}

{cf thumbnail=}
{cf posticon=/wp-content/uploads/posticon.ico}
{cf my_custom_color=#22fb30}

This three examples written inside the post will create three custom fields with respectives values
when you publish the post.
After publishing, the tag inside the post are deleted. No other information is erased.

= Notes =

 Because the way the plugin works, it will run fine with ANY desktop blogger(Windows Live Writer, Scribefire, Qumana, w.Bloggar, Zoundry
, Thingamablog, Blod Desk, Flock, Post2Blog, Bleezer, you name it)

The plugin can be used even inside the wordpress editor (though what would it be the point?)

-You can use any number of custom field for post.
-Reserved characters: '{' and '}',because it conflicts with the delimiters.
-After the post, the tags are automatically erased.
-If the custom field is already present, its value will be replaced.

== Installation ==

1. Unzip the ZIP file and drop the folder straight into your `wp-content/plugins/` directory.
2. Activate the plugin 'Text to Custom Field' through the 'Plugins' menu in WordPress.

== Frequently Asked Questions ==

* What if I use the tag twice? for example {cf my_custom_value=Anna} , {cf my_custom_value=Jessy} in the same post?
The plugin scans the post from top to bottom and update the custom fields in that order.
In the strange case you do that, the last tag will take precedence over the first one, where
the final value would be **my_custom_value=Jessy**

* Do I need to use quotes (') or double quotes (") to assign values to the custom fields?
No quotes or double quotes are needed. But if you use it, they would be assigned to the custom field, so be careful!

* What if there is already a custom field with that name?
Any custom field with same name is updated

* What if I want to delete a custom field?
This version does not delete a custom field. The best it can do is assign an empty value to a custom field as {cf my_custom_field= }

* Any character or exception to consider?
the '}' can't be inside an evaluation. For example: {cf my_custom_field=hello {there} } won't work as expected since the plugin can't
decide what is the last character. The final evaluation would be **my_custom_field=hello {there**
In the same fashion the character combination '{cf' can't be there inside an assignation.

*What if I have another question related to this plugin?
Contact with for any questions.

== Changelog ==


* using {cf custom_field_name } to avoid conflict with shortcodes. cf is an abreviation of 'custom fields'
* Improved documentation


*Initial release (not for public)

Pages: 1 ... 4 5 [6]