-
AuthorPosts
-
April 28, 2020 at 4:21 pm #1207829
I have trouble with elements displayed differently in Firefox – example: image caption overlay: with Firefox there’s the frame of the caption/text field visible for a moment before it disappears.
Any idea why?Thanks a lot and best regards,
MariekeApril 29, 2020 at 7:05 pm #1208262Hey Leidorf-Media,
Could you please give us a link to your website, we need more context to be able to help you.
Best regards,
VictoriaApril 30, 2020 at 3:21 pm #1208526Hi Victoria,
Please find the website information in the private content section.
Thanks a lot and beste regards,
MariekeMay 2, 2020 at 4:12 am #1209026Hi Marieke,
Thanks for the login details. First off, could you try updating the theme to the latest version (4.7.4) to see if that helps please? https://kriesi.at/documentation/enfold/how-to-install-enfold-theme/#theme-update.
Best regards,
RikardMay 4, 2020 at 6:07 pm #1209635Hi Rikard,
I run the back up right now to install the Enfold Update afterwards.
We have some custom coding implemented – will everything be transferred to the new version or do we have to renew anything afterwards?
Thanks a lot and best regards,
MariekeMay 5, 2020 at 8:29 am #1209835Hi Marieke,
Where exactly did you add custom code? If everything is in a child theme then you shouldn’t have any thing to worry about. If you have added custom code to any of the parent theme templates then that code will be overwritten.
Best regards,
RikardMay 5, 2020 at 9:50 am #1209859Hi Rikard,
Yes, we have a child theme but I’m not sure wether the custom code that the previous agency added before we had some more custom code added by a codeable programmer who implemented the child theme then, is part of the child. I will have the codeable guy take a look at it – just to be on the safe side ;)
All the best,
MariekeMay 6, 2020 at 5:12 am #1210216Hi Marieke,
If you have a child theme then the changes should be implemented there. If the developer who did that is from Codeable then I’m sure it has been properly implemented.
Best regards,
RikardMay 7, 2020 at 2:23 pm #1210723Hi Rikard,
How and where do I get an “Envato private token” ?
Thank you very much and best regards,
MariekeMay 8, 2020 at 7:34 am #1210944Hi Marieke,
Please refer to this: https://kriesi.at/documentation/enfold/theme-registration/
Best regards,
RikardMay 8, 2020 at 1:51 pm #1211024Hi Rikard,
Well the previous agency that we’ve been working with, bought the Theme for us.
They just send me the complete Theme package but I cannot find any licence number in there.Any idea where I can find it?
Thanks a lot and best regards,
MariekeMay 8, 2020 at 8:46 pm #1211191Hi Marieke,
Well, you can try to contact them and try to get access to the Envato account or you’ll need to create your own account and purchase the theme license again.
Best regards,
VictoriaMay 11, 2020 at 2:01 pm #1211836Hi Victoria,
I’ve put in a Token and it has been verified. But obviously there’s no update on Enfold right now as far as I can see…
We’ve version 4.5.7.
I need to fix the https issue soon! All our pages have security issues – how can we fix this???
I updated everything I could and put in the correct links manually where I could.
Why are there still security issues?Thank you very much and best regards,
MariekeMay 12, 2020 at 6:40 am #1212024Hi Marieke,
I tried logging into your site but it’s not loading at all on my end, could you check that it’s up please?
Best regards,
RikardMay 12, 2020 at 10:26 am #1212070Hi Rikard,
It‘s up and running!
neonsee.com/wp-admin
Best regards,
MariekeMay 12, 2020 at 1:55 pm #1212173Hi Rikard,
I’m still thinking about the reason of that https issue.
Actually it might have to do with the way we installed and treated the website:
1. Our previous agency bought and installed the theme on their server, we had access to the staging to do the amendments (http://neonsee.entwicklung-bodenseecrew.de/)
2. The agency moved the website to our Webhoster Hosteurope and named the offline: https://entw.neonsee.com
3. We published the website and renamed domain to: http://neonsee.com
4. I assumed the SSL certificate which was included in the webhosting package would be installed automatically which was not the case, so I did that after the website went online
5. I changed all links manually from http to httpsCan you imagine something went wrong when doing all the transferring steps?
Thanks a lot and best regards,
MariekeMay 13, 2020 at 4:42 am #1212469Hi,
Thanks for the update, I can’t see any problems with SSL on your site at the moment?
About the update; if you select to check manually under Enfold->Theme update then the update will show up. Could you try updating from there please?
Best regards,
RikardMay 13, 2020 at 3:37 pm #1212636Hi Rikard,
Ok, thanks, there was an update which I installed now – but that didn’t change anything for the unsecure issue in Chrome.
Yes, the SSL certificate is active – so far, so good – but still Chrome recognizes the website as unsecure which isn’t good for the ranking in the end as far as I know and in addition to that, it doesn’t look good to potential customers who might be visiting the website with Chrome.
Can the way we treated the website, switching the domain several times be related to the issue?Thank you very much and best regards,
MariekeMay 13, 2020 at 3:55 pm #1212643Apparently there is one link on the Engineering subpage: https://neonsee.com/engineering/
Since there are all pictures properly linked with https, it only can be the Layerslider – which I don’t know how to access that link manually as it’s imbeded via its id.
I already updated the Layerslider Plugin and took the Partners Layerslider of the page and back onto the page – no difference.May 14, 2020 at 11:59 am #1212918Just one comment on the http – https stuff: we are using a theme and didn’t think that we would have to change things manually that often. Is this normal? Shouldn’t the theme automatically update these changes in its “deep” database? I contacted Codeable for this and they told me, they need to do some changes in the database of the theme – of course I need to pay for this. Why?
I have to admit that I’m not a 100% happy with having to pay for the solution of an issue that shouldn’t be there, using a theme!May 15, 2020 at 4:49 am #1213101Hi,
The only problem I could see was the logo URL, I changed that to https and that fixes your problem. You can easily do that yourself in the main page of the theme options.
Best regards,
RikardMay 15, 2020 at 1:48 pm #1213279Hi Rikard,
Thanks for the information but that didn’t change anything regarding the https issue.
We are still recognized as “unsecure” in Chrome.
Means, that we now have to pay to fix something that should automatically work, right?
Is there anything that you can support us with in this case?Thank you very much and best regards,
MariekeMay 20, 2020 at 8:00 am #1214535 -
AuthorPosts
- You must be logged in to reply to this topic.