Forum Replies Created
-
Posts
-
Hi Rikard,
Looks like that fixed it. Must have been a bug in the old version – didn’t like the url change! Thanks a lot.The backend is fully functional except for the pieces that depend on the Enfold theme – specifically, the theme options, and the page builder.
I’ve provided the details you requested privately.Thanks so much,
LindaI just discovered the problem and I fixed it. A good note to myself next time I move a subdirectory install in the future, check and make sure my root directory php settings allow for enough memory! The over memory limit warning did not show up in my admin panel because my subdirectory was set up to allow for more memory, but my root directory was not. Please close this ticket Devin, thank you..
Hi Devin, thanks for the quick response. My htaccess file looks fine, but I did disable and re-enable pretty permalinks to regenerate the htacess file. I am still having a problem with the front page.
Actually, the only time I get the fatal error is with 1 particular page where there are quotes in the title.
Setting the front page in your Theme Options to the rest of the pages are fine. All except the front page. I could create a new page and regenerate the content of the front page, but it disturbs me that this is not resetting for some reason.
Would you like access to my site so that you can see for yourself what happens?
Thanks,
LindaThere seems to be something wrong with whatever is stored in the database for the theme options….. I have tried going into Theme Options and changing the Front Page, and here is where it gets weird:
If I set the front page to some of the pages, I get this: “Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0”
On other pages, it’s fine.
For my chosen front page, it is white screen.
Hi! Just following up!!! Ok I also discovered that all the subpages are fine – this white screen only occurs on the front page!!!! Investigating a little more………. if I find anything I’ll repost here….
Hi Peter,
If you were looking at my link and unable to see the issue in Chrome, it’s probably because I reinstated the code to fix it as our site is going live soon.It seems to be a problem with Chrome (and other webkit browsers) recognizing the multiple nested adjacent sibling selectors….
Hi Devin,
I’m running the most current version WordPress 3.8.1 on my development server and I just upgraded to the latest version on the demo install and the problem persists.I looked into it further, and it seems to be a problem with the visual Avia Layout Builder for this specific case:
– 2 column layout with the gallery on the left
– you click on gallery and then Add/Edit Images, do whatever you need to do, then click Save ChangesThis will result in an extra </p> tag in your markup.
This is easily fixed by dragging your column with the gallery to the bottom of page, and dragging it back to position. Sort of a kludge to fix the problem, but it does remove the </p> tag.
So I think it is a minor bug in your Avia Layout Builder Gallery code.
Since I was able to fix this problem myself, you could close this ticket. But maybe something for the development team to look out for while working on the next release. :)
Thanks so much for looking at this issue Devin. You are the experts so that’s great to know line 207 won’t create any issues in browsers.
Re: the orphaned paragraph tag, you will see that your own theme demo has it as well here:
http://kriesi.at/themes/enfold/portfolio-item/lorem-ipsum/
I did another fresh install on another server and in default editor mode, added 3/4 paragraph & 1/4 paragraph then added a gallery with default photos and it still created the extra orphan paragraph tag at the end.
Hi Devin,
I do think the theme is creating orphaned paragraph tags. I just tested creating a new page using your Avia Builder that has 3/4 column with gallery and 1/4 column with text box – everything empty and the orphaned </p> tag still appears after the avia gallery. I will private reply the link to you.Also regarding the styling tags, I understand you need to create inline styling, but shouldn’t the style declaration be in the header above the body content, not within the body content? This style tag is between the <body> </body> tags.
Not to be such a stickler I guess I could launch the site as it is, but I do believe it should be free of these basic errors……
Thanks,
LindaI’m encountering the same issue. It seems to be a problem with the following nested CSS selectors not being picked up in my browser (latest version of Chrome on MacOS):
@media only screen and (max-width: 989px) and (min-width: 768px) .responsive .av_one_fourth.first.el_before_av_one_fourth, .responsive .av_one_fourth.first + .av_one_fourth, .responsive .av_one_fourth.first + .av_one_fourth + .av_one_fourth, .responsive .av_one_fourth.first + .av_one_fourth + .av_one_fourth + .av_one_fourth, .responsive .av_one_half.first + .av_one_fourth.el_before_av_one_fourth, .responsive .av_one_half.first + .av_one_fourth.el_before_av_one_fourth + .av_one_fourth { margin-left: 4%; width: 48%; }Instead this gets picked up:
div .av_one_fourth { margin-left: 6%; width: 20.5%; }I can pm you my site (which is in demo) to show you.
Hi! I just wanted to say I am new to Enfold and I wanted this same functionality and your edits work brilliantly Yigit. This is a great forum topic, thank you!
I feel as if this topic should be highlighted as I imagine there are many users (for example the user who posted item #227928 on forum) who probably would like the gallery with thumbnails to perform without the full lightbox opening up on mobile browsers / ipads / etc. rather they would prefer to have the image appear in the “fake” lightbox window when you click on thumbnail.
Thanks for listening!
Linda
