My name is Raice, and I’m writing for the first time in this forum. Usually I prefer to browse through the forums and google rather than creating a thread. This issue looks unique.
I recently came across an issue that I believe someone from this forum can help.
I have noticed that there are more than 100 pages ending with the word “aggregate” that have been created automatically on my website, resulting in a 404 page not found error. I discovered these links from the Google Search Console, and I’m not sure why this has happened.
About a month ago, I redirected all the 404 pages on my website. However, these new links have been created recently, and I’m not sure why. Could it be related to the JavaScript delay feature that I started using with the WP Rocket plugin? I am reluctant to disable this feature because it has significantly improved the performance of my website, and I have spent countless hours to make it work properly.
My main concern is how these newly created pages will affect my SEO. Can you please advise me on what steps I should take to resolve this issue and ensure that my website’s SEO is not negatively impacted?
Thank you for your assistance in advance. I look forward to hearing from someone helpful soon.
]]>I’m using @import statements in my theme style.css to include other CSS files in the theme directory (for organization). I have “Aggregate CSS-files” and “Also aggregate inline CSS” checked. My understanding is that the order of the CSS is intended to be maintained when aggregated. However, I’m seeing that the CSS from the @import statements is at the very top of the aggregated file. Oddly enough, the rest of the style.css file is in the place I would expect (after the parent theme CSS). I would expect the @import CSS to be just above the theme style.css since it is imported at the top of the theme style.css. But it is far above everything else instead (including the parent theme CSS).
Here’s a visual of the order without Autoptimize:
* parent_theme.css
* style.css (contains @import statements)
Here’s a visual of the order with Autoptimize (all aggregated into one file):
* CSS from @import statements
* parent_theme.css
* style.css (just the rest of the file, not the @imports)
I’ve only noticed this change in order to be a problem recently, but it’s possible that it was working before because of a random fluke.
Is this working as intended? It would be nice to be able to keep the order of the @import statements during aggregation.
]]>I have Autoptimize installed on my WordPress site with Optimize CSS Code, Aggregate CSS-files, and Also aggregate inline CSS enable. Excluded CSS are set to the defaults. However, when I go to view Google PageSpeed Insights, it doesn’t appear any of the CSS is being aggregated. All of the individual styles.css, child theme styles, frontend.css, etc show as their own items under render-blocking resources. What could be preventing these files from being aggregated? I also have WP Super Cache and server side caching but disabling these does not seem to fix the problem.
Thank you!
]]>I’ve just started using WP Data Access Premium in earnest and now migrating my existing internal reporting dashboard (written in .NET) to WP using your great plug-in – mainly to speed up ongoing development. However, I’m finding it tricky to implement (what seems to me a simple) particular requirement:
I have the following query which will just simply aggregate values between a date range from a view – like this:
SELECT
retailer_id, vendor_code, company_name,
SUM(num_sales) AS total_trans_count,
SUM(revenue) AS total_revenue
FROM vrpt_rev_daily_by_retailer_v1
WHERE trans_date BETWEEN <<DATE 1>> AND <<DATE 2>>
GROUP BY retailer_id
So effectively it’s summing a column for rows between a given range, for each retailer.
What I effectively want to do on the DATA PUBLISHER is just have a flat table with two dynamic filters (From Date and To Date) – which are used as the aggregate params and that’s it.
In my existing system, I just pass in the two date values and it builds the SQL (as above) and fires it off – but I’m struggling to see how this can be achieved using WP Data Access. Date ranges are a common theme in reporting systems – so some pointers would be great to achieve this. In summary:
1) Can you specify aggregate fields (e.g. SUM() ) ?
2) Can two filter values be passed back in as a BETWEEN clause ?
Or do I need to drop into code to do this – which is what I’m trying to avoid by using this tool?
Cheers
Matt
]]>I’m doing a cleanse of my website’s unused CSS and there are some CSS files currently loaded by some plugins or my theme, which aren’t used, so I’m planning to dequeue in functions.php.
I currently have the aggregate CSS option unchecked in AO, so I have a clearer picture of all CSS filed loaded on my site, but I plan to turn it back on when I’m done.
The question that I have is, will dequeuing the original CSS files in functions.php and then aggregating them with AO work or will AO still aggregate all the files (including the ones I dequeued)?
]]>1. Are there any examples out there of Neve used this way, I could look at?
2. Would I need to upgrade to Neve Pro to take advantage of additional blocks/functionality or could I make a basic Oblique-style grid site in the basic Neve.
3. Any other advice!
]]>Please help, and I am willing to pay for Premium Support if you would offer such an option. Thank you!
]]>