Bilal TAS
Forum Replies Created
-
Forum: Plugins
In reply to: [CodeKit - Custom Codes Editor] Old plugin and upgrade errorsHi @kptgreg, sorry for your inconvenience. I started the refund process, since you don’t need to have PRO license to have that migration feature (and since you want to refund).
Actually once you cloned the site, you only need to update the plugin from the “Updates” page. It should automatically migrate the old codes into the new CodeKit. Did you try updating it directly?
Can you please update it to 2.3.4 and try again?
What are the WordPress and plugin versions on your side?
Can you please update the plugin to 2.3.3 and try again?
Forum: Plugins
In reply to: [CodeKit - Custom Codes Editor] Support Not RepondingHi again, sorry for your inconvenience. I asked a question related to your request.
Hi @jasoncracknell, how did you change your WordPress admin URL? Which plugin or which snippets did you use for that?
Forum: Plugins
In reply to: [CodeKit - Custom Codes Editor] support does not respondHi @renom82, so sorry for the problem we experienced with our support system. We recently started using this support form. If you don’t mind, can you please re-submit your issues here?
I tried refunding on our system but it doesn’t allow me to do it at the moment. However, I could be able to extend your license one more year for free.
Sorry again for your inconvenience.
Hi @kreativrudel, thanks for the bug report. We have released 2.3.2 version today to prevent that possible conflict. The new structure only for multisite WordPress is “WP_CONTENT_DIR/custom_codes/site-<blog_id>/*”
Don’t worry, it will automatically move the files to correct folder for each site once you update the plugin to 2.3.2.
Thank you again!
Forum: Plugins
In reply to: [CodeKit - Custom Codes Editor] Must-have plugin on every siteHi @magestyx, thanks for the feedback and investigation you did.
The issue you mentioned about PHP functions on CodeKit, it looks like related to the order of releasing the codes. That’s why, I only recommend adding actions from the plugin, or use the functions you wrote on just another PHP Code on CodeKit. You can use “Includes” feature for this.
About the bracket/quote issue, it’s not best practice to update codes on 3rd parties(CodeMirror in this case) files. But if it helps, I can create an editor option which you can completely disable the “Auto Close Brackets” feature. Does that work for you?
Forum: Reviews
In reply to: [CodeKit - Custom Codes Editor] Good Plugin, Great UIThanks for your great feedback, Nabil!
For the point #1, it’s been fixed as of CodeKit 2.2.8. Can you please try doing that again?
#2: Can you please expand the issue?
#3: Yes, you’re absolutely right. It’s on our roadmap. Filenames will be changeable.
Looks like you’re using “ftpext” WP filesystem method instead of default “direct” method, and not configured it. This is why you’re getting this error. As of 2.2.5, you’ll get an admin error notice which says “Your WordPress filesystem method “ftpext” is not configured correctly. Please configure it, or use another method like “direct” to be able to continue using the plugin.”
Forum: Plugins
In reply to: [CodeKit - Custom Codes Editor] Always Fail To Add Custom FunctionHi @wootechno,
You just need to add opening PHP tag at the beginning of the editor. So it will be:
<?php add_action( 'wp_footer', 'woocommerce_show_coupon', 99 ); function woocommerce_show_coupon() { echo ' <script type="text/javascript"> jQuery(document).ready(function($) { $(\'.checkout_coupon\').show(); }); </script> '; }Forum: Reviews
In reply to: [CodeKit - Custom Codes Editor] The safe mode feature saved me!You’re always welcome! 🙂
Forum: Plugins
In reply to: [CodeKit - Custom Codes Editor] Vue.js errorThank you so much for informing, Tom!
It’s just have been fixed on version 2.2.1. Can you please update and let us know whether or not the issue still exists?Forum: Plugins
In reply to: [CodeKit - Custom Codes Editor] Public Side SCSS/CSSHi Fred,
Looks like it’s about the location you select. If it’s on “Everywhere”, acts like you mentioned. You should select “Frontend” option to make it applied to only frontend.
For the SCSS settings, you can simply create an “Settings” custom code and @import it into the custom code you are working on. That’s the easiest solution for the free version.
Please let me know if you still have any issue.
Thanks,
Bilal