cablop

Bump!

really? not a single answer on this?

I did a check on the generated tar file. It is not what i expected.

You are truncating the names of the files, so they are useless for me now. This is not how a backup is supposed to work. And i can’t go with zip format, because it is taking hours to compress a 1~1.5 GB backup.

This is so frustrating.

But this is a workaround, this clearly must be part of the Shop Manager capabilities. It is bad we should need 2 plugins to fix the bad behaviour of this one.

Can i suggest that instead of removing the whole Aux tab just leave the “Entire website” and “Website Backend” options, and maybe the “404 Error” one too?

I think those 3 cover the minimum that other free alternatives currently cover.

Por otro lado, los clientes de Bogotá ya estan acostumbrados a buscar Bogotá -> Bogotá en las tiendas en línea como son Mercadolibre y OLX que son referente al momento de implementar los ecommerce en el país.

• This reply was modified 3 years, 9 months ago by cablop.

De hecho esta solicitud se había hecho anteriormente y se respondió que Bogotá pertenecía a Cundinamarca, aunque no es el caso. Ni la clasificación del DANE ni la de la DIAN lo muestran de esa forma:

• DANE: subregiones.pdf
• DIAN: Codigos_municipios_2007.pdf

El código de cada municipio consiste en 5 dígitos, los dos primeros corresponden al departamento, los tres finales al municipio. En el caso de Bogota es 11001 (que se usaba como “ZIP” antes de que pusieran los códigos postales actuales); 11 corresponde a Bogotá y 11001 corresponde a Bogotá D.C. El código de Cundinamarca es 25 y no 11.

• This reply was modified 3 years, 9 months ago by cablop.

Wow, so the “Entire website” option is going to be removed?

That is going to break a lot of websites.

• This reply was modified 3 years, 9 months ago by cablop.

En las Zonas de Envío de WooCommerce solo deja escoger por departamentos, no deja escoger por ciudades, lo probé hace menos de una semana.

Bogotá no es parte de Cundinamarca, Bogotá es parte del D.C., y el D.C. no está entre los departamentos. Debería estar el D.C. (o Bogotá D.C.) y dentro solo Bogotá. No está bien poner a Bogotá como ciudad o municipio de Cundinamarca.

Is CJT open source and available in some repository? I think the way the community can contribute to the plugin is by coding. I know how to code and i can contribute to, at least, help in keeping CJT compatible with WP updates in order to help people with existing sites with CJT – like me – to keep those sites woring without issues. No need to add more features, just proposing some developers can help to keep the plugin alive and maybe trim it a little bit.

I like to see you are reading what we users have to say and to take those things into consideration.

I’m sorry i have to give a short answer now, but i also want to provide an answer, and more deatils later.

I understand it is hard to maintain such big plugin, but also it’ll be bad to lose the userbase the plugin already has. It is good to hear you’ll keep both plugins for some time in oder to make an easier transition. It’ll be good if you find a way to ask current users what are the most used features. But i’m afraid those are the features i mentioned, specially:
– Entire Website, that help users to modify or extend themes.
– Custom Post Types, tags and custom taxonomies, because this is what they use for things like products in e-shops.
– The footer, because this is how we easily add things like the Google Analytics and other tracing codes, without touching themes and independently of any current, past or future theme the site will use.
– The ability to turn blosk on and off… just because we cannot just delete and recreate code blocks during maintence time.
– And maybe some auxiliary features.

@manakio2k i find your attitude highly out of place… you are just looking the situation from one side, not from the points of view of the many actors involved in a succesful plugin.

When there are good websites that were built around some functionalities of a plugin and then that functionality becomes removed in the free version, websites break, even to the point of become unusable. Clients are eager to pay to developers of plugins that break their websites. You need to be responsibe with your loyal customers and CJT is a plugin that was here for many years and many major versions (8 in total) with many users and stable websites.

The notice on the CJT plugin says “we have dropped support and updates for CSS & JavaScript Toolbox”. So is is a matter of months, even weeks, for the websites to break because the current CJT version will be not compatible with a future WP release. To move to ECM is impossible, because ECM has less features. To fork CJT is not practical, because that will directly hurt ECM interests.

The webmaster who maintains the website, not made it, also worries about it. And he is not going to get more work just to keep CJT or ECM in the website. He’ll just look for another option and walk away. And you’ll lose customers that way.

If you have a nice useful and working solution, you can involve your community and find a way to move forward for a better future, @wipeoutmedia and @xpointer.

Hello. @wipeoutmedia and @xpointer.

My intention is not to hurt your project. I really understand that a software project needs funding. But to make a decision that can break websites is a bad move.

From my experience, clients don’t understand it. Place yourself in the customer’s shoes: they find a free feature, they built a nice website on top of it, then suddenly the feature becomes paid. They feel like betrayed, that that was just a bait to get them. I was in such a situation before, the site heavily depended on a free plugin, they updated it, but removed many many features moving it to the paid plugin, the site becomes broken and unusable. I told my client to purchase the pro plugin, but she plainly said “how i’m supposed to pay to the people who broke my website? go find another solution, i prefer to pay for a different solution but not these guys”. The trust was lost. She is not able to trust those developers anymore so we had to find other solutions and wipe everything related to that plugin out.

This plugin is very useful and we used them also in e-shops. Clients with e-shops are so demanding and of course they hate when their source of profit can get hurt from a plugin. They’re not developers, they see the world from the point of view of money.

And i say that because the CJT plugin says its development stopped. There was no reference saying the plugin will be updated, and we know what that means. In a matter of months, WP will be updated and CJT starts to fails once the changes made them uncompatible.

I don’t know what else to say. I think there should be a way to keep your loyal base of current users… and not to make them look like they’re forced to upgrade, but make them want to upgrade.

• This reply was modified 7 years, 5 months ago by cablop.

It is sad to see this plugin gping the ransomware way other plugins did in the past. That is to take free features sites are currently using to force the purchase of the “Pro” version. So sad to see this happen.