Forum Replies Created

Viewing 15 replies - 1 through 15 (of 22 total)
  • Thread Starter sunilwilliams

    (@sunilwilliams)

    Hey Nirbhay.

    The problem has come again on another site.

    It persists when I change themes and disable all plugins except for elementor and dashboard welcome.

    Thread Starter sunilwilliams

    (@sunilwilliams)

    Hi Nirbhay.

    It’s been a few days since I looked at this project.

    I just logged in to it now and the dashboard is present.

    Thanks.

    I’m in this boat as well.

    I can set a template to a course. But the setting isn’t applied in practice.

    I can’t see this issue being addressed at all anywhere.

    Just to confirm, I’m also seeing this same undesireable behaviour.

    When I click the ‘save’ button I get a message saying that the tokens have been saved. But when I reload the page the fields for the tokens are blank.

    Thread Starter sunilwilliams

    (@sunilwilliams)

    I figured it out.

    In order for any settings under ‘Advanced Options’ to take effect, the option ‘Enable Advanced Options’ (also in the Advanced Options tab) needs to be enabled.

    Thanks.

    Thread Starter sunilwilliams

    (@sunilwilliams)

    Hi all.

    This might be resolved. For reasons unrelated to this post, I restarted php-fpm and apache.

    After that, the jetpack admin page showed me a warning: an xml extension for php wasn’t available.

    I installed the php-xml module. After that Jetpack connected.

    Thanks.

    Thread Starter sunilwilliams

    (@sunilwilliams)

    Fair enough.

    I’ve edited my review and I’m happy to give it 5 stars:
    This plugin is so useful that I install it by default on most of my sites.

    Thanks Marco!

    Just in case anyone else finds this thread over the next few hours.

    Updating from Custom Field Suit version 2.5 to 2.51 solved my problem to.

    My site showed this message and nothing else:

    Fatal error: Call to undefined method cfs_init::get() in /home/mysite/mysite.com/current/public/content/themes/drtmnyc/head.php on line 27

    I could not log into wp-admin. https://mysite.com/wp-admin also showed this message.

    Updating to 2.5.1 solved this issue.

    On another site I did not see this message. However, the frontpage was blank. I was able to log into the admin.

    Again, updating to Custom Field Suite 2.5.1 fixed the problem.

    Both themes used custom themes.

    Thanks for the fast fix Matt! Great product. Great service.

    I see what you mean: the checkout page isn’t being styled.

    Watching the network, I can’t see any ‘404’ http responses for stylesheets.

    At this point I’m afraid I can’t be of further assistance. You’d need to get help either from someone who has direct access to the site, or who has a better understanding of headway.

    I’d recommend contacting your previous developer or getting support from the theme vendor.

    Ok. I’m looking at the site and I can’t see anything obviously wrong. I’m looking across the home, blog and contact pages.

    Can you describe these two things:

    * What you expect to see

    * What you are seeing instead.

    You’ve got a few possible ways forward:

    * Go back to the developer that you paid. Make an arrangement with them to repair your site.

    * spend time within the headway documentation: https://docs.headwaythemes.com/

    * Pay for support from headway.

    The quickest way may be the latter. I looked at their pricing page, and currently they are advertising a discounted rate.

    If you want help on these forums:
    “scrambled and weird looking” isn’t quiet good enough as an issue description. It’d help to link us to the site.

    Can we please talk about software licensing without making sexist remarks?

    I’d personally prefer this conversation and the forum generally not being hostile to members of our community that are women.

    Well, first of all it’s really distasteful to use a metaphor that assumes a woman is the property of her father. Or that her choice of partner is somehow a violation of a fathers property rights.

    I suggest that if we continue this converstion, that we don’t use such horrible metaphors.

    Secondly: I don’t see how Landing Pages did anything unethical. They simply created a derivative work from software that explicitly permitted them to, as announced in the license of the original work.

    If there was a violation of ethics then where is it? Which ethical principle is being violated?

    yet Elegant Themes still chose to be constrained by the GPL” is not really accurate nor fair

    It’s certainly accurate. I own a licensed version of Bloom that I purchased from ELegant Themes. So I checked their license. At first I thought that if ET were displeased, then there must be a license violation. So I opened up the file called ‘license.txt’.

    At the very top is this:

    Copyright 2015 Elegant Themes, Inc.

    All plugin files are licensed under the GNU Public License 2.0 unless
    specified as otherwise within the file itself. Some files may be
    licensed under alternative open source licenses such as MIT, BSD
    or OFL. Refer to individual files for licensing information. If no
    license is stated, then the file is placed under the GPL 2.0. You
    will find a copy of the GPL 2.0 below.

    I then scanned the other files included in Bloom. The only other license notice I could find is the MIT license bound to idletimer.js, either derived or copied straight from a file published by Paul Irish.

    So there you go: Elegant Themes has chosen to be constrained by the GPL.

    After that block of text, the GPLv2 is published in full.

    If Elegant Themes did not choose to be bound by the GPL, then sometime in their years of doing business they would have not used it as a license for their own software.

    (Of course that would mean that they would have published software for a platform other then WordPress.)

    There’s very little to digest. The GPL is very clear and written in plain English. The preamble sums it up even more clearly.

    Any company that bases it’s business model around GLP’d software simply has to read it.

    “That’s legal in terms of GPL but morally wrong.”

    If code authors believe that this behaviour is morally wrong, then they should use a license which doesn’t so easily and explicitly enable it.

    The GPL is very clear about it’s what constraints it does and does not carry. And it’s been around for so long that the moral issues have been widely discussed across many programming and business communities.

    And yet Elegant Themes still chose to be constrained by the GPL.

    Personally, I’m a happy customer of Elegant Themes. I think they are great and I’m going to continue doing business with them.

    But Leadpages did nothing ethically and they clearly didn’t violate a license.

Viewing 15 replies - 1 through 15 (of 22 total)