Forum Replies Created

Viewing 15 replies - 31 through 45 (of 84 total)
  • Thread Starter mobilewebexpert

    (@mobilewebexpert)

    I’ve just upgraded to the Pro version, which has the “HTML editor” option.

    However, I still have the same problem – that is, my apostrophes and double quotes are still being preceded with a backslash.

    I’ve also tried replacing with @quot; but that also doesn’t render as hoped.

    Thread Starter mobilewebexpert

    (@mobilewebexpert)

    Thanks.

    Thread Starter mobilewebexpert

    (@mobilewebexpert)

    (THIS IS A RE-POST WITH BETTTER FORMATTING)

    I have a custom taxonomy that contains 3 terms. And I have numerous CPT (custom post types) posts assigned to those terms.

    I want my menu to look like this:

    MY TAXONOMY
    – TERM 1
    –– CPT 1A
    –– CPT 1B
    –– CPT 1C
    – TERM 2
    –– CPT 2A
    –– CPT 2B
    –– CPT 2C
    – TERM 3
    –– CPT 3A
    –– CPT 3B
    –– CPT 3C

    Therefore, I am using “Populate from taxonomy” option with these settings…

    Taxonomies: my-cpt-taxonomy
    Terms: All
    Depth: 10

    …which I presume is correct(?). But the menu that is produces is just:

    MY TAXONOMY
    – TERM 1
    – TERM 2
    – TERM 3

    I.e., the second level of depth (my CPT items) is not shown – despite me specifying a depth of 10.

    Does anyone know how I can fix this problem so my CPT items are also shown? (NB, I still have this problem even after creating a brand new CPT item, so the problem is not date-of-post related.)

    Thread Starter mobilewebexpert

    (@mobilewebexpert)

    Turns out this was a core charts.js issue.

    To achieve a linear x-axis, you have to use a scatter chart and use the showLine attribute.

    As an example, here is my test index.html:

    <!DOCTYPE html>
    <html>
        <head>
    	<title>Chart.js Test</title>
    	<meta charset="UTF-8" />
    	<meta name="viewport" content="width=device-width, initial-scale=1.0" />
    	<script src="https://cdn.jsdelivr.net/npm/[email protected]"></script>
        </head>
        <body>
    	<div>
    	    <h1>Chart.js Test</h1>
    	    <canvas id="myChart" height="100" aria-label="Hello ARIA World" role="img">
    		<p>Sorry, your browser cannot display this chart.</p>
    	    </canvas>
    <script>
    
    var ctx = document.getElementById('myChart');
    var myChart = new Chart(ctx, {
        type: 'scatter',
        data: {
            datasets: [{
                label: 'Data 1',
                data: [{
                    x: 0,
                    y: 78.818216388591
                }, {
                    x: 0.018,
                    y: 78.8177145560425
                }, {
                    x: 17.982,
                    y: 43.4801632630024
                }, {
                    x: 18,
                    y: 43.444332540587
                }],
    	    showLine: true,
    	    pointBackgroundColor: '#fab100',
    	    borderColor: '#fab100',
    	    backgroundColor: '#00000000'
            }, {
                label: 'Data 2',
                data: [{
                    x: 0,
                    y: -0.033143033735255
                }, {
                    x: 0.018,
                    y: 0.037985464562535
                }, {
                    x: 17.982,
                    y: 36.7758176230439
                }, {
                    x: 18,
                    y: 36.7763082632964
                }],
    	    showLine: true,
    	    pointBackgroundColor: '#aab200',
    	    borderColor: '#aab200',
    	    backgroundColor: '#00000000'
            }]
        },
        options: {
            scales: {
    	    xAxes: [{
    		scaleLabel: {
    		    display: true,
    		    labelString: "My x axis",
    		    fontColor: "#fab100"
    		},
                    ticks: {
    		    min: 0,
                        max: 18,
    		    stepSize: 1,
    		    
    		    callback: function(value, index, values) {
                            return '' + value;
                        }
    		    
                    }
                }],
                yAxes: [{
    		scaleLabel: {
    		    display: true,
    		    labelString: "My y axis",
    		    fontColor: "#ff0000"
    		},
                    ticks: {
    		    beginAtZero: true,
    		    suggestedMin: 0,
    		    suggestedMax: 100
                    }
                }]
            }
        }
    });
    
    </script>
    	</div>
        </body>
    </html>
    Thread Starter mobilewebexpert

    (@mobilewebexpert)

    Please would someone direct me to the documentation/tutorial for how to create and display a chart with this plugin.

    Thread Starter mobilewebexpert

    (@mobilewebexpert)

    Sure. Here is the input file for my Chart.js chart:

    Frequency,Data 1,Data 2
    number,number,number
    0,78.818216388591,-0.033143033735255
    0.018,78.8177145560425,0.037985464562535
    17.982,43.4801632630024,36.7758176230439
    18,43.444332540587,36.7763082632964

    Thank you.

    Thread Starter mobilewebexpert

    (@mobilewebexpert)

    I’ve consulted https://docs.themeisle.com/article/728-manual-configuration and tried this code in Manual Configuration box:

    {"vAxis": {"slantedTextAngle": 0}}

    but all it does is make the vertical axis title disappear!

    Please can you provide me with a working solution, thank you.

    Thread Starter mobilewebexpert

    (@mobilewebexpert)

    Please can you provide a more appropriate way to achieve this?

    After all, it appears to be default functionality in WordPress – e.g., you can use <sub /> markup successfully in a page title.

    Thread Starter mobilewebexpert

    (@mobilewebexpert)

    Both the video and the introduction to it need more clarity. For example, introducing introducing the video as “An Inside Look at Prevent Direct Access GoldNot this Free Version” would be clearer. Also, pronouncing the word “gold” correctly (and with more emphasis) in the video would help.

    In addition to being up-front that the user, essentially, is getting next to nothing in this version, I think it wouldn’t go amiss to give the user an idea about the price – especially in this case. That’s because most premium plugins that I’ve come across cost in the region of $10 to $30 to buy outright, whereas your cheapest outright purchase price is currently $299.90. So I think some forewarning of that would be appropriate as such a price would be prohibitive for many users.

    Finally, I don’t agree that “almost all other plugins are doing the same thing” as you in promoting their plugins in the way you are. I’m am experienced developer and I’ve never come across an approach that is as wide of the mark as yours.

    As for the automatic newsletter subscription, this is what the description for your plugin says on my plugins page in wp-admin immediately after activating the plugin:

    Prevent Direct Access is simple way to prevent search engines and the public from indexing and accessing your files without complex user authentication.

    Congrats! You’ve subscribed to our newsletter and now stand a chance to win our 1-year Gold license for free.
    Stay tuned for our updates ??

    …so that’s also a bad sign in terms of support as you clearly do not know your own product.

    Fortunately, I have discovered [a different] plugin, so I will be using that.

    [redacted claims of fake reviews and accusations of insecurity in plugin]

    Thread Starter mobilewebexpert

    (@mobilewebexpert)

    OK, got you. Thanks.

    Thread Starter mobilewebexpert

    (@mobilewebexpert)

    Thanks. I tried that, but it’s made no difference.

    It’s actually a line just above that…

    wp_enqueue_style( 'wpas-plugin-styles' );

    …that results in the wp-content/plugins/awesome-support/assets/public/css/public.css?ver=4.3.5 script being loaded.

    Commenting that out has stopped the stylesheet from being loaded, but it hasn’t helped the UI. It must be the theme we’re using. :-/

    Thanks again for your support.

    Thread Starter mobilewebexpert

    (@mobilewebexpert)

    Thanks for the reply.

    In Tickets > Settings > General > Plugin Pages, I’ve changed the Ticket Submission setting to “None” but it hasn’t made a difference.

    I’m sure it’s not a caching issue.

    If there’s nothing else in the settings to try, can you let me know the code I need to dequeue the stylesheet in my functions file?

    Forum: Plugins
    In reply to: [Arconix FAQ] Ordering

    The FAQs seem to be ordered by title by default.

    If you use this shortcode…

    [faq orderby=”menu_order” order=”ASC”]

    …then the “Order” attribute (that you can enter by doing a Quick Edit on each FAQ) will be respected.

    In my opinion, this “Order” attribute should be the default/primary attribute used for sorting, with the FAQ creation date second, then the title third. This is because I expect most users will enter their FAQs in the order they wish them to appear (not in reverse order!).

    Forum: Plugins
    In reply to: [Arconix FAQ] Ordering

    Same problem here.

    Forum: Plugins
    In reply to: [Arconix FAQ] PHP error

    I have also started seeing an error with this plugin since upgrading to PHP 7.1 – in wp-admin > Dashboard…

    Notice: Undefined property: stdClass::$Array in /home/festiva3/public_html/wp-content/plugins/arconix-faq/includes/class-gamajo-dashboard-glancer.php on line 123

    Also other errors with PHP 7.2.

Viewing 15 replies - 31 through 45 (of 84 total)