leogermani

Hi,

Is it possible to share the URL so I can have a look?

Leo,,

hmmm now I see. Yes, It was a bit confusing, but its ok now.

My installation was already runnin brazilian portuguese and the core wordpress fields all appear in english.

James,

Would you like to test our new version before we release it?

If so, please send me an email at leogermani ar hacklab.com.br

cheers

Leo,,

Hi James,

Do you have access to your server log files?

This could be a memory limit problem. And we are about to release a new version that works around it for sites with a large number of users.

But we have only seen such problem with sites with many thousands of users… thats why I think that it could be something else.

It would be great if you could check your server log files at the time you run the export.

Please test it and write back

Leo,,

Please refer to https://www.ads-software.com/support/topic/plugin-wp-users-exporter-unable-to-activate?replies=6

We will soon release a new version that supports php 5.2

Please refer to https://www.ads-software.com/support/topic/plugin-wp-users-exporter-unable-to-activate?replies=6

We will soon release a new version that supports php 5.2

Hi xrobek,

This plugin requires PHP version 5.3 or greater. We are going to put this information in the docs.

Leo,,

Hi,

sorry for such a delayed responde, its hard to keep track of all posts in the forum.

I dont know what is going on there. But I assure you this has nothing to do with post highlights.

cheers

Leo,,

Hi,

sorry for such a delayed responde, its hard to keep track of all posts in the forum.

It appears to me you simply didnt read the Readme file which explains what you have to do. You dont need to be a geek, you just have to copy and paste a line of code somewhere in your theme

cheers

Leo,,

Hi,

Check if you are not getting any javascript errors on your site.

Ive found my problem,

publicly_queriable must be set to true.

I found that the documentation was misleading the understanding of the public and publicly_queriable paramater.

Hi, I have made a change to the documentation of register_post_type function on the codex. the description of publicly_queriable was using ‘front page’ meaning ‘front-end’. Also, Ive made a better explanation of the public argument.

Ive tested your code on a wp 292 here and it worked.

I noticed there is a javascript error on your site claiming that jQuery.sortable() is not a function, although you have it loaded… It could be that some other plugin you are using is breaking it, or has a conflict with eletrowdgets.

My guess, based on what Ive seen, is that the problem is in this theme. I see it loads jquery (an old version), despite jquery is already loaded by WordPress.. so you have two versions of jQuery loaded at the same time and this could be a problem.

Hi,

I can not see what you are doing wrong. If there is a possibility for you to give me access to your enviroment I would be happy to help you out. email me at leogermani at hacklab dot com dot br

defineAsEletroWidget is used only if you want to have control on which widgets will show up in EletroWidgets. For that to work you have to pass the third paramater as true ( EletroWidgets(0, 2, true) ). Please refer to the documentation.

cheers

Leo,,

Hi there,

I am (or was) working on a similar framework myself and found out pods the other day. Im testing it and have to say that I really enjoy it. I loved that the plugin actually create the tables for each pod – this is what I was looking for.

The possibility of having relationships with WordPress elements and with other Pods are also beautiful… Really.. Congrats for the great work.

Ill you give now my feedback, bringing some ideas I have been working on my CRUD plugin. The thing is I think a plugin like that shoud leave the possibility to developers to change things. The interface is great, but its important to have the possibility to do things that were not planned and are not available in the UI.

What Im working on is totally developer driven, there is no UI, but simple php class you can invoke and create you CRUD passing a model. And the nice thing is that you can extend the php classes and modify the methods to you specific needs. This, added to lots of hooks in the core code, lets you extend and modify the default behavior very easily and with great power.

Why Im telling this? Because I was thinking on improvements to Pods (the porpouse of this topic) and I will list them here… Chances are that I can put my effort on that if you guys think its a good idea.

1. Hooks – Have hooks on the pods code so I can modify it to my needs in a per Pod basis.

2. datatype File – Handle the file upload with wordPress’ media_handle_upload() and, when its an image, have the option to choose wich size you want to display when building your template.

3. sortable – marking a Pod as sortable creates an extra column (item_order) wich is the default field that will be used to order the results. While browsing the content of the Pod, allow you to order items draggin them with jQuery.sortable

4. datatype color – with a color picker

5. Browsing – possibility to choose what fields will be displayed on the list (when the pod has its own menu on the admin); Make the table look more like the rest of WordPress admin area.

Hi there!

Sorry for the delay.

Nice to hear that you enjoy and are using it (I would lova to have some links of sites using it). This was a very early experimental release (0.1 beta) because we wanted more time to write documentation and test it in different situations.

I would certanly help to make eletrowidgets compatible with other plugins, but with the release of WP 2.8 and its new widgets API I think eletro-widgets must be refactored to this new reality. It will be great cause I love the ideia of all widgets beeing multi-instaciable.

So I think Ill put my effort on making eletro-widgets compatible with this new API, and then we can test it again.

By the way, anyone willing to help on that? please leave a message.

cheers

Leo,,