Abigailm
Forum Replies Created
-
Forum: Plugins
In reply to: [Redirection] URL Options – Ignore Slash, Ignore Case – Not availableJust to be clear — on my sites (all on the same server, but different themes on different sites) — here is what I am seeing:
1. Regex — I can select and tick with no problem.
2. Ignore Slash — I can select, so that the box is highlighted in blue, but I can’t click to activate that action. (So box simply stays clear after clicking, and the yellow box to show the selection does not appear above as it does in the image shared by sparker above).
3. Ignore Case — same as Ignore Slash — basically nothing happens other than the selection box being highlighted in blue.Forum: Plugins
In reply to: [Redirection] URL Options – Ignore Slash, Ignore Case – Not availableHere’s a screenshot – https://i.imgur.com/vUOUT6B.jpg
I have multiple sites with different themes that are using Redirect, and I see the same problem on all of the sites.
Forum: Plugins
In reply to: [Redirection] URL Options – Ignore Slash, Ignore Case – Not availableOk. I’m not at my computer now, but I’ll post a screenshot tomorrow.
Forum: Plugins
In reply to: [Redirection] URL Options – Ignore Slash, Ignore Case – Not availableHow would that help? The option boxes display ok… it’s just that I can’t tick the boxes with my cursor. That is, if I put the cursor over the select box an click, there is no response.
I just don’t know understand you want to see in the screen shot.
Will do — just in case anyone else runs into this problem — the user is on an older office desktop system running Windows 7, Internet Explorer 11. I was able to solve the problem for the user for now by rolling back to version 0.8.9.7.
Forum: Fixing WordPress
In reply to: Page Preview not working after WP 5 updateThe issue I reported in this thread was resolved in WP 5.2. It was caused by the way WP handled the sequence of auto-updating when pages had fields with meta-data (common with many themes and plugins, particularly search engine plugins).
So if you have not done so already, you should update to WP 5.2.
Also, many people on github shared information in the efforts to debug and resolve this issue, but no one reported a need to log out as admin as being tied to visibility of the updates. So it sounds like you are experiencing a different problem, that could be tied to a plugin you are using. So I suggest you start your own separate thread if the problem persists.
Forum: Plugins
In reply to: [Quick Paypal Payments] PHP ErrorsThank you. That seems to have resolved the problem (at least no error showing up right now when I tested with PHP 7.3)
Forum: Plugins
In reply to: [Quick Paypal Payments] PHP ErrorsI get the same error if I try to run PHP 7.2 or 7.3 :
PHP Warning: count(): Parameter must be an array or an object that implements Countable in /wp-content/plugins/quick-paypal-payments/quick-paypal-payments.php on line 960
The error doesn’t show up with PHP 7.1. (But note that PHP 7.1 active support ended this past December).
This error has been persistent for a long time — I first reported it 11 months ago.
Forum: Plugins
In reply to: [Event Tickets and Registration] PHP Fatal Error MessageThank you – I was able to replicate the error when I followed the steps you suggested (change to “list” view and click “Previous Events” link). The fix you suggested in lines 3035 & 3036 of the Repository.php file has resolved it.
Forum: Plugins
In reply to: [Widgetize Pages Light] Failed to load …widgetize-pages-light/js/langs/en.jsI’m getting the sense that for plugins like this, which impact page layout & editing, the changes with Gutenberg would require extensive recoding. (So perhaps not so easy for a free plugin with moderate user base – a lot of work without so much reward?)
Gutenberg’s support for some native widgets as blocks coupled with the ability to set reusable blocks may be a workable substitute for many sites; alternatively I think installation of the classic editor makes sense.
Forum: Fixing WordPress
In reply to: Page Preview not working after WP 5 updateOP here — this is now a known bug that has been reported by many users and appears to have gotten worse with the 5.1 WP upgrade. (With 5.0x the preview could be seen with a hard refresh of the preview page; with 5.1 this no longer seems to work and the preview function is simply unavailable on published pages)
This is being followed on github at:
https://github.com/WordPress/gutenberg/issues/12617
&
https://github.com/WordPress/gutenberg/issues/13232I am sure that anyone who is experiencing this problem will be very welcome to share experiences on github, where the focus is not on solving individual user problems but on working collaboratively to resolve more widespread issues. This particular issue is proving very difficult to replicate and resolve, so the more information that can be shared there (on github) the better.
Since I started this topic, I am going to mark this as resolved now- because my question from the OP has been answered, even though the answer is not a fix:
Is this a known bug? YES (for many users) Refer to Github links for more info
Or is it theme dependent? DOES NOT APPEAR TO BE (occurs with many themes, including TwentyNineteen).
Is there a fix or workaround? NOT YET
(I agree that for SOME users the SAME problem might be tied to a theme or plugin, so it always makes sense to rule that out. My answer above is assuming that the problem persists after normal troubleshooting steps have been taken. I’m just trying to make it easier for everyone to comply with WordPress forum rules — since I am no longer looking fo an answer here.).
Forum: Themes and Templates
In reply to: [evolve] Question re changelog for 4.0.6@spartelfant — you don’t have to do anything with plugins or modifications to core files to set up all font choices on a child theme — just put all specifications in your child style sheet. All of the extra fonts are still available to the theme, they just can no longer be set via customizer.
If you set things up with your style sheet, you won’t be able to modify those particular options using the customizer. But you also don’t have to worry about specifications being overridden with a theme update if they are hardcoded into the child style.css file. And once you are comfortable using the style sheet, you may find that to be an easier and faster option than using the customizer in any case. The specs probably do all need to have the !important notation to override the inline styles set by the customizer.
So here is what I would suggest for developing your child theme.
Use view source to find and copy all the inline styles that show up in the section:
<style id='evolve-style-inline-css' type='text/css'> .... </style>Then you can simply override anything you choose in your style.css file.
For example, if the inline style (set via customizer) shows:
body { font-size: 1rem; font-family: Roboto; font-weight: 300; color: #212529; }And if you want the Montserrat font instead, could put this in your style.css:
body {font-family: Montserrat !important;}Forum: Themes and Templates
In reply to: [evolve] Question re changelog for 4.0.6Actually I am happy for others to post in this thread because I think it is important and helpful for others to know what the changes are in version 4.0.6 so everyone can prepare.
I now see is NOT a problem for most design elements on updates as long as no subsequent changes are made via customizer.
But very, very important to back up the database before upgrade!
Here are some other plugins that may be helpful for upgrade process:
My favorite: https://wordpress.org/plugins/wp-rollback/ (this gives the ability to go back to the previous theme version with a simple click) (But note – if there are changes to the customization options, rollback alone cannot restore those — you would need to also restore from the database for that).
Also helpful: https://wordpress.org/plugins/wp-staging/ (This lets you set up a staging site on your own system that is an exact copy of your site so you can safely test out the upgrade without making changes to your live site)
https://wordpress.org/plugins/customizer-export-import/ (This is another way to export customizer settings —so you can use that to backup before upgrade or after you have upgraded, as protection in case you accidentally overwrite settings in the customizer later on.)
https://wordpress.org/plugins/wp-database-backup/ (This is my personal favorite for backing up the database — I put it on all my sites — but there are also many other options for database backup, some that are even more popular. But I always, always, always make a database backup before updating evolve and many other themes and plugins.).
@romik84 — is there an online page that shows the current rules for WordPress theme developers that you have mentioned (“WP requirements, as some parts are plugin territory”)
As Romik says that some parts are “plugin territory” – here is a link to a plugin to replace all fonts– but note that I haven’t used this and don’t know how well it integrates with Evolve.
Fonts: https://wordpress.org/plugins/easy-google-fonts/
Romik — thank you for all that you do. I do agree that it is right and fair for you to hold back extra features for the premium version. I just think it would help if you would let your existing users know very clearly about the changes as it is not too difficult to prepare for them, but much harder to fix a site after things have been lost or messed up.
- This reply was modified 7 years, 4 months ago by Abigailm.
Forum: Themes and Templates
In reply to: [evolve] Question re changelog for 4.0.6Did you by any chance do a database backup before the update? If so you should be able to restore settings as they were before. And then you would also have the option to roll back to the earlier version and delay further updates until you have a system in place to preserve preferences.
I agree with you that a greater selection of fonts is important. But it is also true that that I with most other free themes it is common for features to be limited without an upgrade to premium.
You can also probably restore fonts by hard coding all specifications from before into your custom css. Of course much easier if you can first restore from database to see what they all are. I did make my own copy of current customizer settings so I will have that on hand for the future, in case I accidentally override by making other changes in customizer.
You may also have the option to install plugins that give you the functions you need. More fonts, sliders, maybe also infinite scroll.
Forum: Themes and Templates
In reply to: [evolve] Question re changelog for 4.0.6@nickpapag — how did you upgrade? And were you upgrading from 4.0.5, or from an earlier version?
After I tested on a staging site, I went ahead and upgraded (taking care to first back up the database, of course)– and all my font settings were preserved. I only have one slider, but it is a bootstrap slider with 3 slides, even though now the theme allows for only 2 — but that slide was preserved as well.
I’d note that I am using a child theme and I did not activate the parent theme at any point during the upgrade process. So perhaps that is a reason that my previous settings were preserved while yours appear to have been overridden.
I have verified that my settings are intact – I made sure to clear all caches
So my assumption is that the settings already in the database would be preserved with the upgrade, but potentially overridden in the future if changes are made via the wordpress customizer. I opted to go ahead with the upgrade, because for me it is unlikely that I will make significant changes to site layout & typography in the near future.I agree with you that the changes should have warranted a change to version number up to 5.0, because they represent a reduction in theme functionality and are not backwards compatible.
- This reply was modified 7 years, 4 months ago by Abigailm.
