Forum Replies Created

Viewing 15 replies - 16 through 30 (of 45 total)
  • Thread Starter Flashpaper

    (@flashpaper)

    Lorro, you nailed it! I have been banking my head over this. Thank you so much!

    Thread Starter Flashpaper

    (@flashpaper)

    Interesting. I wish I knew how to do that. Based on your response it has to be something local to my testing server. So, that’s on me. I’ve got some work to do. ๐Ÿ™‚

    Thread Starter Flashpaper

    (@flashpaper)

    Hey there, sorry for going dark. Went on vacation but now I’m back. I was trying to perform a successful migration from CPT UI to PODS ( on a test site running iThemes Builder latest version). I thought perhaps the Builder theme was causing the issue, so I switched to the latest version of the twenty-ten theme…just to try something generic. I’ve got no other plugins running on this test site. But I still encountered the error when running the CPT UI importer.

    1. Select Migrate CPT UI…Import Only
    2. Choose Post Types To Import: Research
    3. Choose Taxonomies To Import: Authors, Period, Research Tags
    4. Select Next Step
    5. Error: Could not insert post into the database.

    I’ve tried running the migration with CPT UI activated or deactivated. Doesn’t make a difference. Pods does create the “Research” custom post type, but none of the taxonomies or Research posts are migrated due to the error. I’ve tried to make this environment as vanilla as possible, but the error is so vague, I don’t know where to even start looking. Thanks for your time. ๐Ÿ™‚

    Thread Starter Flashpaper

    (@flashpaper)

    Ah, interesting! OK, good to know. This plugin is really easy to use and your response times are lightning fast. Thanks for the insight!

    Thread Starter Flashpaper

    (@flashpaper)

    The update seemed to resolve the issue. Thanks!

    Thread Starter Flashpaper

    (@flashpaper)

    Excellent. Thank you so much for the fast reply. Have a great weekend. It looks like you guys have created something very interesting and I look forward to putting it through its paces!

    Cheers!

    Interesting. OK, give me the day test some ideas and I will respond by tomorrow at this time. Cheers!

    Can you provide a detailed, step-by-step workflow based functional description of exactly what is required?

    Hi Josh! Welcome back! Glad to see you again and will continue to support WP-Edit Pro. As I’ve said previously, it’s an excellent plugin…and sometimes “stuff” happens when you run your own company. I totally understand. Cheers!

    Hi Mohsin,

    It is sad. Josh really produced an amazing plugin and from my previous interactions with his company they are really great people. I can only assume something happened to him or his company.

    I haven’t actually found anything that does what this plugin is capable of. I am going to be testing a plugin by thrivethemes.com: https://thrivethemes.com/contentbuilder/.

    But I have no experience with it yet so I cannot say what use cases it best serves. I have a developer who says she can fix the bug I’ve discovered in WP-Edit Pro but I haven’t bothered doing that yet…but I will probably have to since I have built a lot of websites using this plugin.

    If you would like I can let you know what I experience as I begin testing the thrivethemes content builder plugin with both their native themes and the iThemes Builder themes I use for most of my work. I can be reached through my website at michaelpenner.com. ๐Ÿ™‚

    Cheers!
    _michael

    Hi Mohsin,
    I’m a developer in California that has been using this plugin for many years. Even if you get it working, please be aware that the plugin author is no longer responding to support requests, even for those of us who pay $10.00/mo. for the support portal he used to maintain. I don’t know if Josh Lobe has abandoned this plugin, but it is very troubling to pay for support and not get any responses.

    Here’s a problem you’re going to run into (I have the plugin working in 4.7.2 and I reported this problem to Josh on December 15th, 2016 but have yet to receive any response) even if you are not using NextGen Gallery with it like I am:

    When the plugin is active and the the following code is encountered by the Visual Editor, it injects space above and below the code: <div style=”clear:both;”></div>. As one switches between the text editor and the visual editor, the problem multiplies. It becomes necessary to manually remove the spaces in TEXT view and then save only in TEXT view or else the problem replicates if you save while viewing it in the Visual Editor. Deactivating WP-Edit Pro removes this behavior. Bummer! Great plugin though. I am using the SNIDGETS for some rather interesting “ease-of-use” aspects for my clients so they can update site pockets otherwise not accessible to them. Cheers!

    UPDATE: I’ve confirmed that WP Edit Pro and NextGallery are having problems. This is confirmed on WP 4.6.1 and WP 4.7 in a vanilla test environment running the latest versions of both plugins on a test server running php 5.6.

    The problem manifests as repeated, automated injections of code above and below the DIV in the following setup:
    1. Type in the DIV manually or use the WPED CLEAR BOTH tool. In Text mode, the resulting code looks like this <div style=”clear:both;”></div>
    2. Switching now to the Visual Editor will automatically inject and addition above and below the div. If you stay in the TEXT editor, this behavior does not occur.
    3. However, if the code on the page appears like this, then the problem does not occur: <div style=”clear:both;”> </div>. For some reason, the existence of a space within the DIV stops the issue from happening.

    Hi Serge,

    I am just a user of this plugin, but I sometimes see this behavior when there is a conflict with another plugin. I have also seen it behave oddly when security settings I configure conflict with what it needs. If you use iThemes Security Pro or WordFence, or any security plugin, then consider trying different things with those plugins, such as turning them off, or allowing file writing permissions, etc…

    Hope this helps!

    OK, so here is where a language barrier might not be serving your company well. Those files your plugin copies to the a subfolder called /wpi of the current theme, are not related to the website’s current theme. So a more accurate way of saying this is: “The Client Dashboard has it’s own default theme that you must override with a set of template files we provide so you can manually approximate the design of your website for that page. The Client Dashboard currently will not adopt your current theme like the Invoice page will.”

    Once I understood that and stopped trying to make this thing “work with any theme” (can you see why that is confusing when you say that?) I was able to move forward with my project…although now I have lost 2 days trying to figure out what I did wrong only to realize I did nothing wrong (for once…usually it really is my fault!).

    I’ve sent an e-mail to Elena as well, encouraging your company to review the way it communicates about it’s plugin capabilities. Your products are really really good. It would not have mattered to me that the Client Dashboard has this limitation. I would have used it anyway and let my client know that the workflow would be modified. It might be a language barrier. I have some Swiss-German clients that often say things that don’t quite translate into what they intended, so to me it appears that might be what is happening here. I hope my feedback will help you correct that communication problem on your website and in your technical documentation soon, because I really like your plugins and I really intend to keep on using them!

    Cheers!

    So, any page designated as the Client Dashboard or the Invoice Page will never fully adopt the current theme or display it’s content within the current theme?

    Thanks Maria! I’ll be sure to test that out once I’ve got the dedicated SSL in place on my staging server. Cheers!

Viewing 15 replies - 16 through 30 (of 45 total)