Mark Smalley

Transparency has always been of the up-most importance to me, which is why I labelled the initial release as 0.1 and we are still at 0.2+ – as well as responding to each and every question regarding its state of affairs, but you seem to be demanding answers to impossible questions. I will be returning to this project when my boss tells me to, or when I have the time to take on paying freelance work that will allow for continued development. Exactly (or even roughly) when that will be is impossible to say, and whether this project (GeoPress and all continued work I do on geo-location) remains in MySQL and WordPress when I do is a whole other issue of its own. Feel free to fork the project, and as someone recently reminded me…

” If you are not entirely satisfied with the product, please feel free to request a full refund ” ??

To be clear, I am the only person that was working on gPress, and did so in my spare time. At the time of starting development on it, I had a dead-end job and ample spare time. Since then, I got married, had a kid and found a job that is truly fulfilling, where we are currently developing our own OpenSource NoSQL CMS system – https://mongopress.org

Like any community, there are a lot of good folk, but with any community as large as this one, there are also lots of undesirable unappreciative idiots. In all my time where I was actively developing gPress, I only ever had one truly helpful support request, where most of my “support” time was spent asking people to confirm if it was a conflict with one of their other plugins or a non-standard theme they were using (which about 90% of problems were). I mean; seriously, try to be more active in your bug reports – investigate and play with the code and try to give a developer a helping hand, even if just pointing him or her towards a possible fix – this stuff is OpenSource, you have it at your fingertips and can help change the world! I was once contacted on Christmas day practically ordering me to stop what I was doing and help fix some site where my plugin conflicted with one of the other 600 plugins that they had installed. I’ve had vicious and depressing emails, repetitive DMs and and all kinds of nonsense from people with very little if any appreciation. On top of that, my plugin was remove twice from the repository and my personal user account here across the WordPress network was even deleted once – with the only possible “official” explanation having been that it was more than likely an over-zealous contributor. All of this, coupled with the fact that I now have a family that I need to spend my precious time with has made it extremely difficult to continue working on things…

But that’s not without trying. I took on a few “geo-relevant” freelance projects that allowed for additional features to be added, and I even managed to sell the concept of my plugin to the new company I worked at, where we started developing a huge BuddyPress project that’s added a lot of stuff to the latest unreleased version (including geo-spatial polygon generation and proximity queries along with OpenStreetMap integration and enough funk to wet your pants all days long), and has even resulted in the development of 3 new “high-end” plugins that have also not been released. However, that project and our commitment to the WordPress community was put on hold at around the 80% completion mark when we started experimenting with MongoDB and quickly found an extreme distaste for anything based on the antiquity known as MySQL. Coincidentally, this was about the same time we started developing MongoPress.

When time permits, I will certainly return to this project – in some-shape or form, and in the meantime, my thanks to everyone that did have something positive to contribute, and will hopefully see you again on the otherside…

To all the trolls, “SO LONG, AND THANKS FOR ALL THE FISH” ??

There’s a good chance the query_posts function injected into the header to allow for places on the homepage may be affecting the plugin.

Have you read the documentation about this…?
https://gpress.my/documentation/

You should be able to de-activate the query on the homepage through the plugin options and then manually configure the loop as required…

Unless of course you are seeing some specific JS or PHP errors, which I do not see in the screen-shot…? With errors, I have something more substantial to track down…

Where is the conflict taking place?

Is it a back-end problem, or one on the homepage, or all pages?

If you could help me isolate the issue, I will be able to resolve things on my side much quicker, otherwise I will need to download the DCG plugin once I get the chance and try to track things down myself, which could take some time…

The taxonomies and reference to names can all be changed via the .po files, making it quite flexible, but yes, in its EARLY beta state, it does not do much, other than adding places and maps – the beauty is in its future, where things will soon become very interesting, as seen in our roadmap – https://gpress.my/roadmap/

This should be resolved with gPress 0.2.5+

Could you please take these issues to the official support forum over on BuddyPress.org as they are easier to manage and track – https://buddypress.org/community/groups/gpress/forum/

Since 0.2.5, more hooks and filters have been added as seen in documentation at https://gpress.my/documentation/

These errors are due to Foursquare, which are prime reasons why Foursquare functionality was removed from gPress 0.2.5 – please upgrade and let me know if you run into any new problems…

gPress 0.2.5 should hopefully fix all these issues, but will only work with WordPress 3.1+

Please let me know if anyone still faces problems after upgrading…

Would be happy to add more hooks and filters, but have just released 0.2.5, which drastically changes things, so please double-check if this is still required urgently and where things need to be added.

Also, please continue this in BP.org gPress forums if possible….

This should now be resolved in gPress 0.2.5 as Foursquare functionality has been completely removed from core.

This problem should have been resolved with the new 0.2.5 version released today, so please upgrade, test and let me know…

gPress is in a VERY early beta stage – its only version 0.2.5 now, but in saying that, the last version, just uploaded this morning has had a LOT of upgrades, and should hopefully fix / resolve a lot of problems people were facing, so please upgrade and let me know…

We are looking at ways to incorporate other sources, as seen in our roadmap – https://gpress.my/roadmap

gPress was recently upgraded to version 0.2.5, so please download and re-test, then let me know if there are any new issues…